exclude some fields of RFx for workflow

[Former Member]

Workflow experts,

Using sRM7.0 process controlled workflow.

We would like to exclude few fields for triggering workflow..u.

or...as a workaround, we want that only auatomatic workflow is triggered if the value changes in those fields.

Kindly suggest how can I achieve it.

Ganapathi

[Former Member · Accepted solution]

Hi,

Can you please explain your business requirement little detail.

Saravanan

[Former Member · Accepted solution]

Dear Saravanan,

Thanks for the response. We have already configured the process controlled workflow for RFx and it is working fine.

Now the business requirement is that, for example

The buyer is given a default authority to extend bid submission deadline for certain days, by a cercular.

So I need to insert a logic, if the submission deadline is extended for XX days, it should not trigger workflow (or it should trigger only automatic workflow).

How can I insert this logic? Can you give some ideas?

Ganapathi

[Former Member · Accepted solution]

Hi,

if submission deadline is extended for XX days, you want to release the RFx without routing for approval right? then create a custom function module expression. insert the logic in the expression to check the XX days of submission. if its true then ev_value is 'X' or ev_value is space.

compare the express with each process level. if this expression is 'x' then do not trigger the process level which will end up to trigger the automatic approval.

other option is to determine the dynamical process schema, if the above condition is true then only automatic approval process level else normal process. please let us know if you need more information.

Saravanan

[Former Member · Accepted solution]

Dear Saravanan,

Thanks for the response.

The solution which you have proposed is fine. But we are getting confused and feeling that it is tricky, for example, if the user changes some other field(s) also along with the admissible changes in submission deadline, then the work flow should be as usual. In such cases, if I had written a logic to check only changes in 'submission deadline' then it would not trigger the normal approval process, even if a significant changes are done in other fields? If I have to avoid this, then I may need to check all the fields whether those changed?....then the question comes what are those fields... perhaps then I may be landed to exteremly complicated logics..?

Whether my confusion is correct? Or Is there any BAdI where I can insert my logic, even before the workflow is triggered?

Ganapathi

[Former Member · Accepted solution]

Hi,

the change document details will be loged into cdhdr and cdpos tables with change and new values. try to compare.. let us know if you need more information.

Saravanan

[Former Member · Accepted solution]

Dear Saravanan,

Thanks for the response.

cdhdr and cdpos records are getting created for many fields of RFx. I am

able to ovserve same in 'tracking tab' of RFx.

My worry is,

If I have to avoid this, then I may need to check all the fields 
whether those changed?....

How can I achieve

 if the user changes some other field(s) also along with the admissible changes in submission deadline, then the work flow should be as usual.

Ganapathi

[Former Member · Accepted solution]

Dear Sarvanan,

Could you please give your further response / openion about my query...

Thanks.... Ganapathi.

[Former Member · Accepted solution]

Hi,

CDHDR & CDPOS will update all the values for that transaction, i think you have to check all the fields to trigger the WF or have a custom field in the RFx and based on the custom field is flag trigger the WF..

Saravanan

[Former Member · Accepted solution]

Dear Saravanan,

Thanks for the responses to my questions.

Ok... it seems that is the only way... will go with long way! Closing the thread.

Ganapathi

[Former Member · Accepted solution]

Dear Saravanan,

How are you?

I am re-opening this thread, would like to explore on some more ways....

Recently I read about table in the thread

where I can set the TYPE as

I Structure/Field Enters Comparison (inclusive)

E Structure/Field Does not Enter Comparison (exclusive)

for the selected fields in COMPARISON METHOD

SYS System Default Setting (always read as basis)

VUI Version Comparisons for Interface

CRV Comparison When Creating Versions

UWF Comparison at Update of Active Documents from Change WF

VWF Version Comparison for Workflow Attributes

CDI Version Comparison for Contract Distribution

PCO Version Comparison for Purchase Order Confirmation

POO PO Output

CCT Transfer Contract Data to Catalog

INV Version Comparison for Invoice

BII Version Comparison for Bid Invitation Internal View

BIE Version Comparison for Bid Invitation External View

FCD Version Comparison for Corresp.Structures (Hdr,Item,Set)

NWF Version Comparison for n-Level Workflow

OWF Version Comparison for Workflow Call-up

BIQ Comparison of Bid and Bid Invitation

BBQ Bid Comparison

SPO Version Comparison for SUS Purchase Order Confirmation

POR Version Comparison for Purchase Order

but I do not see any entry for VWF in this table, as standard delivery, but it is possible to add... would it serve my purpose?

Is it relevant for "excluding some fields for RFx for workflow?".

Ganapathi

[Former Member]

re-opned the thread to explore some more ideas.