Complex Email Notification

Question

Hello Forum,
I am trying to achieve a complex situation. I want to notify changes in a resource form field. The targets of the notification are:
- The user
- The operator that makes de change
- IT Crew responsible of the resource
The main problem is that in the email body I have to notify who has made the change. For that purpose I am using <Assignee Profile Information.User Login>.
If I configure the Notification Tab to "User" and "Asignee" I am able to get the login of the person that made the change, but to notify the IT Crew I am using the assignement tab with email send (the adapter of the task is tcCompleteTask), if I configure this assignement, the variable <Assignee Profile Information.User Login> looses its track of the real person that made the change.
There is any way, trying to avoid coding, that lets me notify to a group of users who made a change in a form of another user?
Thanks in advance,
Regards,
Xisco.

Answer 1

Going with the deferred task example you'd have to do something like this:
(Again, it doesn't have to be a deferred task.)
<Action id="0" name="Add Deferred Task" application="com.waveset.session.WorkflowServices">
    <Argument name="op" value="addDeferredTask"/>
    <Argument name="type" value="User"/>
    <Argument name="name" value="$(accountId)"/>
    <Argument name="subject" value="Configurator"/>
    <Argument name="task" value="Your Workflow Name"/>
    <Argument name="date"> <!-- date the deferred task is to execute -->
        <ref>date</ref> <!-- precalculated date -->
    </Argument>
    <Argument name="date_task_added">
        <!-- add the time the task was actually registered -->
        <invoke name="getTime"> <!-- calculates "now" -->
            <invoke name="getInstance" class="java.util.Calendar"/>
        </invoke>
    </Argument>
    ... other deferred task arguments here
</Action>IDM will wait until the date the task is to be executed, see the "date" argument. When IDM actually executes the deferred task (it may be a long time after it was originally scheduled to execute if there's been a delay or an outage or whatever) you'll have a variable in your workflow called "date_task_added" that should be a java date object. (Or a string, I can't remember. If it is you'll just have to convert it, no biggy.) That will give you the date the deferred task was registered. Within the workflow you can build another date object using the exact same code to calculate "now".
From there getting the time difference between both objects is a simple matter of getting the milliseconds for each and doing the math to get the difference. That's just one way, there's dozens of ways of calculating time differences with the java date and calendar objects.
Note: untested code. You may have to tweak it to work properly.