Backordered check box on RITM

[Jason Stephens]

I have a user who wants to use the 'backordered' check box to denote an order that he hasn't finished fulfilling. He may have 250 out of 500 widgets and is waiting on the other 250. I wanted to make sure that OOB, checking this doesn't trigger any unwanted side effects - we just want to use as a placeholder. It appears to me that this is the case, but I wanted to ask to make sure. Is there anything happening behind the scenes when the 'backordered' check box is used?

[MB26]

I do not see that "backordered" is used in any business rules, client scripts, UI Policies, or UI Actions on the Request Item table. The only place that I do see it used is in the workflow. The OOB "Service Catalog Request Item" workflow example uses the "backordered" field to notify the user if in backorder. If you are using a different workflow that does not use this, it would appear that you should be fine.

[Ivan Martez]

If you go into the demo instance under Workflow application -> Workflow Versions module. Select the Service Catalog Item Request workflow -> Workflow Activities related list -> Asset Mgmt. Fulfills Order record. In this record there is a related list called "Workflow Conditions", this is where backordered is specified. You can place a condition on this workflow condition. In this case there is a field on the catalog task called "Backordered", if the person working the ticket checks this off and saves the record, it will set that flag to true and follow its path within the workflow.

These are user made conditions and this is only setup this way as an example and should not impact any other workflow you may have.

[Anish Reghu]

Dear @Ivan Martez,

I guess the "Backordered" field is on the RITM and not on the catalog task? Excuse me, for my lack of understanding, if the above one is said in a different context.

Best Regards,

Anish