As part of
IDBCHRS-34, the change detection mechanism has been updated such that the user will not be required to select the relevant "EAI Type" field, as this is believed to be too advanced for the goals of Identity Broker v4.0 (in particular, the "Parts" type). These require the user to have full understanding of how chris21 is sending its data back to Identity Broker, down to the position in the string returned, and be able to interpret the result in full.
The mechanism has been updated such that a large majority of forms are completely covered by the changes. However, some forms return change data which cannot be directly mapped back to a chris21 request, such as the ALW form:
The key for the form is made of 5 components, but things can be of varying lengths. Compare the above key data with:
Under the old mechanism, the user would need to add a Parts type and manually enter the position of the second key in the string in order to use EAI.
Given this complexity, investigate the success of the current changes to change detection for user requirements, further investigate the wrapping of these keys, and also consider alternate change mechanisms to overcome this apparent limitation (such as seeing the impact "Changes enabled" has on file tables).
A dictionary has been added for additional handling of specific forms in the future. Specific forms should be investigated and added to the dictionary.
Customer support service by UserEcho