MeetingRegistrationIssue
When is this issue thrown?
This issue is raised internally by the API when a meeting or session is added to the order if the business rules dictate it. Meetings and sessions normally have a limit on the amount of people that can be registered and waitlisted. When a meeting or a session is added to the order/shopping cart, the system validates whether or not seats are available. If the seats are not available, the system then checks to see if seats are available on the waitlist. If both the registrar and waitlist are full, the system does not allow the meeting or session to be added to the order.
This validation can be thrown for these reasons:
• There is no capacity and no waitlist capacity available. • There is no capacity, but the waitlist is available.
• There is no capacity available, but the product allows you to Override Capacity (not available on the Web).
• When you place an order for a meeting/session for which the registration date has passed.
• When you exceed the maximum number of tickets allowed for a session.
ProductOutofStockIssue
When is this issue thrown?
The ProductOutOfStockIssue is raised when a product is selected on an order detail line. The OrderDetail object is responsible for raising the issue. The constructor for the issue class requires only a product ID and product name. The product ID is used for the Reference property and the product name is used as a parameter for constructing the message. The class determines the unique key for the issue and contains constants defined for all of the messages that it needs. The class also contains a CanBackOrder property and an
AddAlternateProduct method. These are used by the OrderDetail object to control the behavior of the ProductOutOfStockIssue.
What is the message/response?
When the CanBackOrder flag is set to TRUE, the issue class adds a response, with the appropriate message and a response value of “Continue” to its responses collection. It then sets this as the default response for the issue. When AddAlternateProduct is called, a new
OrderInfo Validation Issue Examples response is added to the responses collection specifying the appropriate message and using the ID of the alternate product as the value for the response.
Invoking the ProductOutOfStockIssue
The following code shows how the OrderDetail object would invoke the
ProductOutOfStockIssue. This would be called when the order detail object determines that the product is out of stock. The code creates a new ProductOutOfStockIssue, passing the
OrderInfo Validation Issue Examples product ID and product name on the constructor. It then sets the CanBackOrder flag to true, and adds three alternate products.
InvalidDateRangeIssue
InvalidDateRangeIssue is an issue class that reports an invalid date range. The issue accepts an Owner object, a StartDate, and EndDate on the constructor. It uses the Owner object to create a unique key for the issue an stores the StartDate and EndDate in private variables. The class does not set a message string in the constructor, rather, it overrides the message property and returns one of three messages depending on the contents of the StartDate and EndDate properties.
CustomerInfo Validation Issue Examples
CustomerInfo Validation Issue Examples
AddressValidationIssue
This validation issue alerts the user as to the results of the Address Validator. The Address Validator application is used to validate customer addresses.
When is this issue thrown?
This issue is thrown when the Address Validator completes its function. For example, Group1 has completed its run and needs to inform the user of its results.
What is the message/response?
There are two messages. If the address validation is successful, a message similar to, “Address has been validated. No errors. Continue?” displays. If issues arise with the Address Validator or an exception has been raised, a message similar to, “Address cannot be validated”
followed by the error/exception displays.
How do you resolve this issue?
If the address validation is successful, no action must be taken. If an error was raised by the Address Validator, the address must be corrected and re-validated. If an exception occurs, contact your System Administrator.
What are the implications of this issue?
SegmentWithMembersDisabledIssue
When is this issue thrown?
This validation issue is raised when the user attempts to disable a segment definition for which there are existing members.
What is the message/response?
“Members exist for this segment definition. Do you want to turn off Segmentation?” The message also displays the rule, description, and qualifiers for the segment definition. This requires a Yes/No response.
How do you resolve this issue?
Since this is a Yes/No issue, the user must choose to either leave the segment definition as is or turn off segmentation.
What are the implications of this issue?
The segment definition is turned on/off based upon the user’s response.
SegmentChangeWithMembersIssue
When is this issue thrown?
This issue is thrown when the user attempts to change a Segment Definition for which there are existing members.
What is the message/response?
“Members exist for this segment definition. Do you want to continue with the change? The message also displays the rule, description, and qualifiers for the segment definition. This requires a Yes/No response.
How do you resolve this issue?
Since this is a Yes/No issue, the user must choose to either leave the segment definition as is or allow for modifications to the segment definition.
What are the implications of this issue?
The segment definition is turned on/off based upon the user’s response.
UpdateSubCustomerStatusToReflectMasterCustomerStatusIssue
This validation issue updates the Customer Status Code of Sub Customer when the master record is being updated.
When is the issue thrown?
This issue is thrown when the user updates the Customer Status Code and the customer has Sub Customer records linked to it.
What is the message/response?
CustomerInfo Validation Issue Examples This requires a Yes/No response.
How do you resolve this issue?
Since this is a Yes/No issue, the user must choose to either update the sub customer record(s) with the modified Customer Status Code or not.
What are the implications of this issue?
The Customer Status Code of the sub customer record(s) are updated or not based on the user’s response.
MarkAddressAsBillToORShipToIssue
This validation issue alerts the user of a potential duplicate primary customer address and updates of the customer’s Primary Address flag depending on the user’s response.
When is this issue thrown?
This issue is thrown when the user adds a new address or edits an existing address and marks the address as the primary address when a primary address already exists for the customer.
What is the message/response?
“Another address is marked as the primary #1# address. Should the new address become the primary #1# address?”
This requires a Yes/No response.
How do you resolve this issue?
Since this is a Yes/No issue, the user must choose whether or not to update the primary address flag.
What are the implications of this issue?
The primary address flag of the customer may be modified based upon the user’s response. A customer can only have one primary address.
CreateMultipleLinksToPrimaryAddressIssue
When is this issue thrown?
This validation issue is thrown when a user creates a new address and attempts to link that address to another customer.
What is the message/response?
“Cannot link to the company record entered because this company’s primary address is already linked to customer #1#. Link this record to #1# as well?”
This requires a Yes/No response.
How do you resolve this issue?
Since this is a Yes/No issue, the user must decide whether or not to proceed with linking the addresses.
EmailExistAsPrimaryForAnotherCustomerIssue
When is this issue thrown?
This issue is raised when a user creates a new primary email address for a customer, attempts to save the record, and the email address is already being used as the primary email address for another customer record.
What is the message/response?
“Email address already exists in Personify as a primary email for customer #1#. Do you want to set this email as primary email for current customer?”
This requires a Yes/No response.
How do you resolve this issue?
Since this is a Yes/No isssue, the user must decide whether or not to use the email address as the primary email address for both customers.
PrimaryEmployerAlreadyExistsIssue
This validation issue alerts the user to the fact that the customer already has a primary employer on record and updates the primary employer flag based upon the user’s response.
When is this issue thrown?
This issue is raised when the user creates a new primary employment relationship for a customer and attempts to save the record.
What is the message/response?
“Primary employment already exists, do you want to update existing primary employer information with new information?
This requires a Yes/No response.
How do you resolve this issue?
Since this is a Yes/No issue, the user must decide whether or not to update the primary employment flag of either of the customer’s employment relationship records.
What are the implications of this issue?
The newly created relationship record is either set as the primary employment relationship or not based upon the user’s response.
There can be only one primary employer for a single customer record. Customer records can have multiple, non-primary employer records.<Check validity of this statement>
PrimaryContactAlreadyExistsIssue
This validation issue alerts the user to the existence of a primary contact relationship for the customer and updates the primary contact flag of the customer’s relationship depending on the user’s response.
CustomerInfo Validation Issue Examples
When is this issue thrown?
This issues is raised when a user creates a new primary contact relationship for a customer and attempts to save the record.
What is the message/response?
“Primary contact already exists, do you want to update existing primary contact information with new information?”
This requires a Yes/No response.
How do you resolve this issue?
Since this is a Yes/No issue, the user must decide whether or not to update the primary contact flag of either of the customer’s contact relationship records.
What are the implications of this issue?
The newly created relationship record is either set as the primary contact relationship or not based upon the user’s response.
There can be only one primary contact relationship for a single customer record. Customer records can have multiple, non-primary employer records. < CHECK>
DuplicateCustomerMatchesFoundIssue
This validation issue alerts the user of a potential duplicate customer match based on criteria set up for the application to match a duplicate customers and contains a list of the possible duplicate customer records.
The user can choose to continue with the customer’s creation or select one of the identified duplicates.
When is this issue thrown?
The issue is raised upon the user’s saving of a newly created customer record.
What is the message/response?
“Duplicate Customer Match Found for <LabelName>. Do you want to continue?” This requires a Yes/No response.
How do you resolve this issue?
If the Personify UI displays a screen with a data grid displaying the duplicate customers found, the user can either select one of the presented customer records or continue saving the record.
If not using the Personify UI, the validation issue will contain “DuplicateCustomerIds” property, which displays a list of the potential duplicate customers.
What are the implications of this issue?
The newly created customer record can either be saved as is or the user can select one of the duplicate matches to work with.