2 Replies Latest reply on Aug 12, 2014 7:33 AM by Aryan Anantwar

    Update WorkOrder fails if triggered from remedy.

      Share:|

      Hi All,

       

      I am stuck at this. I create a filter on entry created in workorder which invokes a process to restart a windows service and update status of workorder back when the service is restarted. In the process I have a windows command and update entry. I am using context as input to entry-id to update WO. The whole workflows works fine when tested from DevStudio. But when triggered from remedy side, the process gets triggered but and when the update entry is executed, instead of requestid in place of <entry-id> ReuestId </entry-id> I get this <entry-id> WO </entry-id>.

      when triggered from remedy filter.

      <items>

        <item>

          <schema>WOI:WorkOrder</schema>

          <updated-field>Status</updated-field>

          <updated-field-value>5</updated-field-value>

          <entry-id>WO</entry-id>

        </item>

      </items>

      When triggered from Devstudio see the log. It is the same when triggered from filter but the request id is replaced with WO.