Use Case Name
Touchpoints are the point of action which when triggered transfers informations between the schema/entities. This happens when the attributes of the source entity are mapped with the attributes of the destination entity of that touchpoint. Touchpoints are needed to be triggered in an order as each touchpoint’s serves each purpose.
For Instance: Before triggering the touchpoint
INVOICE ADD, the touchpoint ORDER ADD is needed to be triggered before and before triggering
CUSTOMER ADD or BUSINESS PARTNER ADD is needed to be triggered.
This is done to remove discrepancy with the customer records. So this raises a dependency factor among each of the touchpoint.
Implementers, Developers, Partners.
Organisation Creation & Connection Creation.
APPSeCONNECT has the feature to setup these dependencies and is categorized accordingly:
1.Pre-Task: This kind of dependency is when the related touchpoint needs to be synced ahead of the primary touchpoint.
2.Post-Task: This kind of dependency is when the related touchpoint is needed to be synced immediately after the sync process of the primary touchpoint. Therefore instead of triggering the sync process two times, dependency setup can be done for the primary touchpoint.
3.In-Process Task: This kind of dependency is when the user requires to halt the operation of the primary touchpoint, for getting the related data from the source application in order to execute the related touchpoint. The primary touchpoint will resume immediately after the related touchpoint executes.
For Instance: Suppose before executing the touchpoint
ORDER ADD an
In-Process Task is executed for the touchpoint
Business Partner Add where, all the orders will be fetched but will be halted for the related touchpoint to get synced.
This is done to reduce the discrepancy with the data alignment. Like if the Business Partner Touchpoint is synced
all the customer would be fetched, and after a minute the ORDER ADD touchpoint is synced now the discrepancy might happen
as within that period of time some more order might appear. Therefore, the In-Process Task is initiated to reduce the
4.Post Acknowledgement Task: This kind of dependency is implemented when the result from the primary touchpoint is served as the input of the related touchpoint. For e.g. order increment id of sales order serves as the primary key for the invoice add.
5.Post-Input Task: This kind of dependency is implemented when the data fetched from the primary touchpoint serves as the source data of the related touchpoint.
For Eg: In case of the Order
add touchpoint and the Guest
Customer Add touchpoint, the data fetched from the source of the primary touchpoint
(in this case, Order Add) acts as the source data for the related touchpoint, letting both the task to work without any discrepancy.
- Need to have a valid APPSeCONNECT Account.
- Create connection for which the dependency setup is to be done.
- Create Touchpoints if any of the application used is a custom app.
- Make sure the touchpoints are active, before setting up the dependency.
- Login to the APPSeCONNECT portal and Navigate to the touchpoints page.
- Select the touchpoint which will be acting as the primary touchpoint (in this case, the touchpoint used is Invoice Add). Click on the dependency icon in the touchpoint.
- The Dependency setup page opens up. On clicking the expand button, the node expands up to show the dependency touchpoints present. On clicking, the PLUS Symbol (in BOLD), new node opens with the field present to setup the dependency.
- In the drop-down menu of the field EVENTS all the dependency tasks are displayed. Click on any of them for selecting the task.
- Select the related touchpoint from the drop-down list, for which the dependency is to be setup. And click on SAVE.
- Similarly other touchpoints can also have dependencies and in the similarly way the setup is to be done for any other dependency task required.
The user can view the successful sync of the touchpoint Invoice Add as in this case.
The user can view the error logs in the RESYNC Bucket of the agent (Cloud and OP), if the touchpoint fails to sync for any cases.
Frequency of Use
The user can sync the touchpoint whenever required.