Skip to main content

I’m using a BPA to update the value in this field: 

The update is succesfully made in the database:

But the page does not reflect the change:

 

Is this a limitation of this particular assistant window?

 

The page is Inventory Parts In Stock - select a row - Handling Unit - Attach to Handling Unit

 

The virtuals are 

INVENTORY_PART_IN_STOCK_HANDLING_ATTACH_PARTS_TO_HANDLING_UNIT_VIRTUAL_VRT
and

INVENTORY_PART_IN_STOCK_HANDLING_PART_IN_STOCK_TO_ATTACH_HU_VIRTUAL_VRT

Hi ​@paul harland 
Are you in the same assistant step and wondering why the “Aty Attached” is not updating?
If so, there is no mechanism implemented to update or partially update assistants UIs after workflow executions.
 

hi ​@Buddhi Gunasekara 

thanks for the reply

It seems to work fine in many assistants e.g. we can observe a change happening in one field, and the BPA can update another field - and then we can see the changed data refreshed into the page.  I wonder if there is a built-in page refresh on that assistant and not on this one, would that make sense?   

I did some further investigation into this today

There are a couple of approaches that work:

  1. If you trigger the BPA as the Assistant starts, you can update the values in the virtual, and the new values will be displayed in the assistant  when it opens.  To do this you can use an IFS API update task.
  2. If you want to make a change triggered by a value being chosen in another field, you can do this using a Process Enrichment task with timing Before.  But i think it only works within the same Virtual.  

The problem in my original post is that i am trying to trigger on change as in (2) in the parent virtual, but i’m making the update in a child virtual, which does not get refreshed.

I think this must be the limitation.

Reply


Terms & ConditionsCookie settings