This section describes the general tasks required to configure the system to support the integration. It also describes the service task type portal.
Refer to the Supported Functionality section for addition details about configuration required for specific business functionality.
Review the base messages provided for communication of positive and negative responses to the self service user. These are configured on self service task types.
Confirmation Header message. The product provides a base message that may be used, with message category 11126 and message number 11723. The base message text may be overwritten. Or a new message in a message category reserved for implementations may be created.
Error Header message. The product provides a base message that may be used, with message category 11126 and message number 11010. The base message text may be overwritten. Or a new message in a message category reserved for implementations may be created.
Create a managed content record to define the HTML to use for the various general emails.
Create one for emails routed to a responsible user when problems are found with the master configuration table.
If confirmation emails should be sent to taxpayers when tasks with multiple steps are complete, create a managed content entry for that email text. If different service tasks should have different general text in the confirmation email, create a separate record for each variation.
The Managed Content Type should be HTML. Navigate to the Schema tab and enter the following tags and type the appropriate text for the email within the "<span>" tags.
<html> <body> <span> </span> </body> </html>
Verify that an XAI sender is configured for routing email real time.
Invocation Type should be set to Real-time
XAI Class should be set to RTEMAILSNDR
On the Context tab, the context type SMTP Host name should be defined with a valid context value.
Define a field that includes the text for the email subject for the notification of master configuration errors email.
Define one or more fields that include the text for the email subject for the confirmation emails to send for the various service tasks.
If any service task should send a confirmation email after all steps are complete, for example once a payment is processed, configure one or more appropriate algorithms for the C1-SSCONFREM algorithm type.
Set the Email Subject field created above for the confirmation email.
Set the Predefined Text to the Managed Content created above for the confirmation email.
Enter the From Address that should be used in the generated email
Enter the XAI Sender for Email defined above.
Base product is provided with the implementation of access type Tax Role with keys PER_ID and TAX_ROLE_ID. If required, additional access types should be added to the lookup USER_ACCESS_TYPE_FLG.
Base product is provided with the implementation two Lines of Business: Individual and Business. If required, additional line of business entries should be added to the lookup LINE_OF_BUSINESS_FLG.
Create a Self Service Master Configuration record that holds system wide configuration needed for the self service integration.
The Configuration Support section defines information needed to alert a user that problems were found with configuration. The alert may be sent using a To Do entry or an email or both.
Define the user that is responsible for technical issues related to self service who should receive an email if there is an issue.
To Do Type should be set to a standard error To Do type to use when issues are found with the master configuration table. The base product To Do Type Self Service Master Configuration Issues (C1-SSMCI) is provided for this purpose.
To Do Role should be configured to an appropriate default To Do role for the above To Do type.
Populate the following fields if an email should be generated when configuration problems exist.
Enter the From Email Address that should be used in the email.
Enter the From Name that should be used in the email.
Enter the XAI Sender created above or leave it blank to use the default from XAI options.
Set the Email Content to the Managed Content record created above.
Set the Email Subject field created above.
Provide the Configuration Support Email Script that produces the email. The product has supplied C1-SSIssueEm which may be used here.
The Request Processing Control information allows an implementation to define special logic that should occur when a web service is processed. The special logic may be causing an inquiry audit record to be created or it could be to indicate a custom extension to a base product service by retrieving additional details to return in a web service call.
To Do Type for Audit Script Errors should be set to an appropriate To Do type. The base product To Do Type Self Service Task Audit Issues (C1-SSAI) is provided for this purpose.
To Do Role for Audit Script Errors should be configured to an appropriate default To Do role for the above To Do type.
To Do Type for Custom Extension Errors should be set to an appropriate To Do type. The base product To Do Type Self Service Task Custom Extension Issues (C1-SSCSI) is provided for this purpose.
To Do Role for Custom Extension Errors should be configured to an appropriate default To Do role for the above To Do type.
For any web service that requires inquiry audit or custom extension, determine the schema associated with the XAI inbound service that processes the web service.
Schema Type and Schema Name should be set to the appropriate object that the XAI inbound service references.
For enabling inquiry audit, check the Inquiry Audit Enabled button. If the raw XML of the request and response should be captured, check the Store Response Data checkbox. Indicate the Audit Script. The base product provides the script C1-AddWebAI that may be used.
For providing additional data in a web service response, provide a Custom Extension Script. The schema for the custom extension script should match the schema that it is extending. It populates data in the data area C1-SSCustomExtensionFields.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]