Handling Composite Type Requests

Question

Hey Gentlemen,
It's an honor writing my question in a forum that contains the best brains in the Identity management field hoping that you will help me in dealing with a problem i'm currently facing in a project i'm working on.
The scenario i'm working on is that when the Synchronization engine adds or removes a user from a security group in FIM Portal an action workflow should run to execute different actions depending on which security group this user was added to, for example,
if the user was added to the Enable AD Security Group then an action workflow will trigger to execute a script to enable the user that was added to the security group AD Account.
After implementing this scenario, i noticed that when only one update is propagated to the FIM MA all my action workflows and scripts work fine because this single request will contain all the information i need (Target Group, Person added to the group),
but when two or more updates is being populated those requests are joined in a composite request and then separated in the portal because each one of those requests will trigger a different workflow. 
However when the requests gets separated they will only inlcude the target group and don't inlcude the GUID of the Person added to the group and therefore all my custom workflows and scripts fails.
Does anyone of you have any idea of how could i force the synchronization engine not to join the requests in a composite type request?
Thanks in advance,
Majd

Answer 1

Hey Brain, thanks for replying to my question, let me explain further the problem i'm facing:
The request i want to process is coming from a BHOLD Management Agent which adds a user to a security group in the mataverse, when an export is done on the FIM MA management agent i'm most interested in knowing the GUID of the member added to the group,
below is the request parameters of a single request coming from the synchronization engine to the FIM Portal.
<RequestParameter xsi:type="UpdateRequestParameter"><Target>263ea811-748f-42f6-8bd1-f8ae68397d0f</Target><Calculated>false</Calculated><PropertyName>ExplicitMember</PropertyName><Value
xsi:type="q1:guid">f5588f39-edb0-4668-a0aa-590488a6fba4</Value><Operation>Create</Operation><Mode>Add</Mode></RequestParameter>
you can notice the GUID of the member added to the security group, however when the Synchronization engine combines them into one request and i try to run a custom script of workflow the requests get separated but without a GUID attribute as in the request
parameters below.
<RequestParameter xmlns:q1="http://microsoft.com/wsdl/types/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="SystemEventRequestParameter"><Target>09f4b1f5-401f-4d46-8ae7-327a776e737b</Target><Calculated>false</Calculated><WorkflowDefinition><Value>14678a3c-4e4f-4d8a-9d85-6ed36c9065a9</Value></WorkflowDefinition></RequestParameter> 
Notice that the GUID of the person added is missing which makes my whole custom workflows and even email templates fails because i depend on the value of the [//Delta/ExplicitMember/Added] which is not present in this request parameter.