ShadowClient

The ShadowClient is an attached rule, which can be used to shadow the rejected clients and policies that were created while processing the incoming interface (such as AsFile) when the system encounters validation errors. The configurer can attach the rule to a company level activity.

Note: Once shadowed, the client shall not be visible/searchable.

  • This rule can take a single client GUID or an array of client GUIDs as input and change the status of the client to shadow. A single client GUID can be passed in the form of activity field or a math variable.
  • A "business error" shall be thrown in case shadowing on the client is attempted in an invalid scenario, which will not be override-able.
  • On reversing the activity for which ShadowClient is attached the activity shall get reversed but shadowing of the client shall not be reversed.
  • If the mandatory element ClientGuid is missing/empty in the rule, then the system error indicating "CLIENTGUID not provided" shall be displayed.
  • When a transaction is initiated with attached business rule ShadowClient to put the client in shadow state then, the following conditions/validations shall be evaluated for each client in the input before the activity is executed. If the condition fails, the message stating "There are Roles or Activities attached to one or more of the given clients that need to be manually reversed/deleted. Shadowing of the client cannot be processed.."will be displayed.
    • Validation for Activities that have completed some processing:
      1. There should be no activities in a status where there is some processing (lightening bolt action) beyond just addition of activity has been already performed: TypeCode = ‘01’ or ’04’; StatusCode not in ‘02’, '09', ‘12’ and ‘34’; i.e. all types of activities shall be considered for this check - both program and non-program; both spawned and user-added; both Normal and Recycle activities.
      2. If there is one or more activities with some processing (statuses defined above), the system shall display the above error.
    • Validation for Roles in “Active” status for which the Client is the Role Player:
      1. There should be no Role records in AsRole table (Policy roles) or AsAgreementRole (Agreement level roles) or with this Client as the Role Player that is in “Active” status.
      2. The policies which are not in Shadow status should be considered.
      3. If there is one or more Policy or Agreement roles in “Active” status – the system shall display the above error.
ShadowClient Elements and Attributes
Element/Tag Definition Attribute Element/Attribute Value and Description
<ShadowClient> Opening and closing tag of ShadowClient. This rule changes the status of the client to shadow.

 

 
<ClientGuid> Mandatory, Non-repeatable: ClientGuid attribute holds the GUID of the client to be shadowed. This can be single GUID or an array of GUIDs to be shadowed.    

 

XML Schema

<ShadowClient>
<ClientGuid>1234</ClientGuid>
</ShadowClient>