In our previous post from July 26, 2019 we discussed how to create
the V2 Application Analysis Ruleset - AARS.
Below we will add to the post, to show end-users how to add logic to notify user(s) when an EDI or Application Route is not found.
In the Version 2 Application Analysis Ruleset, we will test against the return value(s) of,
1. Set-up Variables
We will set-up the vRouteList and vRouteListSize variables as seen above.
2. Set vRouteListSize to 0
In the picture above we will set
vRouteListSize to 0 . This will be done by performing a Move Rule to
3. GetApplicationsRoutes Target/Return Code
In the Output/Target of GetApplicationsRoutes we will map vRouteList
4. Check LisSize of vRouteList
After we map vRouteList in step 3, we will check the value.
- If vRouteList is greater than 0 we will call the ruleset rules: AssembleContext and ExecuteContentRouter.
- If vRouteList is equal to 0 we will call the ruleset rules to create an error notification.
By: Sean Hoppe on