The community will be in read-only from Monday 11:59pm (PT) to Wednesday 7:30am (PT)
The community will be in read-only from Monday 11:59pm (PT) to Wednesday 7:30am (PT)
Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Can we update Request Status(out of box) field from backend to reflect request status

Highlighted
Phanishwar
Collector

Can we update Request Status(out of box) field from backend to reflect request status

Hi,

Is it possible to update Request Status field from backend from execution steps of the workflow.

We have a business requirement where depending on a field(F1) values request status would be different . I mean we have flow like exec step->Decision Step->exec Step-Decison Step(like that). The status at Decision step would be the status of the request type in PPM that's fine. The constraint here is Can we call a proc at Exce steps to update request Status field to use one worklfow flow(as above) instead of creating one flow for different values of the Field(F1) to show different statuses.

The out of box request status field shows value what status name you have at decision step of it's workflow. Is that we will not be putting any status name on the workflow' Decision steps so that by backend update we can leverage the same decision steps to show different request status by calling proc at exe step behind them.


If possible what are the tables need to be updated.

Thanks,
Phani
2 REPLIES
Phanishwar
Collector

Re: Can we update Request Status(out of box) field from backend to reflect request status

I updated backend table update kcrt_requests set status_id=3 where request_id=214046 , status id could be found from kcrt_statuses table. It's working..

Thanks!!
himanshukumar
Super Collector

Re: Can we update Request Status(out of box) field from backend to reflect request status

Phani,

If based on the field value you need to show changes only in the statuses dependencies then the above backend would work fine. But if the request needs to follow a different path or traverse different steps based on the field value then the backend update would create data inconsistency in the system.

Thanks!
Himanshu
//Add this to "OnDomLoad" event