The solution that I know about that issue is to use de audit functionallity of tables. Then you have to use a workflow manual in batch mode to send the email associated to the audit.

For example, in the case you need to know when a delivery is created with a particular delivery mode you need:

1- In table SDELIVERY activate Audit with creation an workflow selected and then with field MDL to be audited.

2- Create a new workflow rule type manual and with a model similar to UPDFLD linked with SDELIVERY instead of ATABLE or ATABZON. Then in the header conditions enter [F:AUD]STA=2 and in line conditions [F:AUL]COL="MDL" and [F:AUL]NVAL=4 (for example).

3- Remember to activate mail and action and in the Action insert AWRKUPDFLD similar to UPDFLD workflow to update AUDITH table.

4- Finally enter a batch task that executes SAIWRKMAN with the workflow rule you have created and when it is executed it would send a message and update the STA field of AUDITH.

This would send messages always a new record in SDELIVERY is created with MDL equals 4 in every way you insert a record in SDELIVERY.

The solution that I know about that issue is to use de audit functionallity of tables. Then you have to use a workflow manual in batch mode to send the email associated to the audit.

For example, in the case you need to know when a delivery is created with a particular delivery mode you need:

1- In table SDELIVERY activate Audit with creation an workflow selected and then with field MDL to be audited.

2- Create a new workflow rule type manual and with a model similar to UPDFLD linked with SDELIVERY instead of ATABLE or ATABZON. Then in the header conditions enter [F:AUD]STA=2 and in line conditions [F:AUL]COL="MDL" and [F:AUL]NVAL=4 (for example).

3- Remember to activate mail and action and in the Action insert AWRKUPDFLD similar to UPDFLD workflow to update AUDITH table.

4- Finally enter a batch task that executes SAIWRKMAN with the workflow rule you have created and when it is executed it would send a message and update the STA field of AUDITH.

This would send messages always a new record in SDELIVERY is created with MDL equals 4 in every way you insert a record in SDELIVERY.

I took a few stabs at this yesterday but was unsuccessful as well. I'm not very familiar with the models and the set up of a new UPDFLD, nor the ACTION portion of the workflow rules. Would you be willing to shed more light on those two areas Jorge?

Hi Mirabelli,

I think the problem it's not working is because you are checking the Simulation flag in the SAIWRKMAN task. I want to attach my steps working in a PDF but I don't know how to add a PDF so I published a link:

www.evernote.com/.../

Oh I See. Yes I have it working now. I was under the assumption that the e-mail would fire after the actual INSERTION of a SDELIVERY record with MDL = 4. Basically from what I understand, this WF has to be setup as a recurring task or programmed to run at set intervals during the day, it won't just fire everytime the audit table is updated (ie. a delivery is created with mode = 4)?

I still can't quite get this to execute. We are on v6.5 utilizing the web client, maybe that's causing issues. As you run the SAIWRKMAN function does anything result, a log file or anything of the like?

I was able to get the pop-up W/F screen.

Hi Bryan,

We are too on v6.5 so I don't think it's the problem. You have to test that the audit table updates to Precessed and isf so the problem is on your mail server (if you are using a web client I don't know if you can use the client mail.

Hi Mirabelli,


Yes it's right. It's only working in a recurring task. If you want it to be launched very insert you need to develop in every process that creates a shipment and don't have a workflow a call to a workflow.
For example, in FUNPREDLV entry point, in AUTDLVMAJ you can add a call to the workflow required and is not need of audit table but you have to detect all the processes that creates a shipment.

In this reply say how to do that:
sagecity.na.sage.com/.../100041

AUDIT WORKFLOW.docxThanks Jorge. Bryan, I outlined step by step what I did to get my workflow to fire. I tested it with ENDDAT on MFGHEAD. Here are my steps.

Hop this helps.

Although I should note that my filter [M:MFG]MFGSTA = 1 isn't working. I'm assuming that's the way the data model is structured and I don't know if there is a way to alter this to reflect changes in externally linked tables aside from AUDITH and AUDITL

Just figured this issue out , on the MFGHEAD table under Audit tab, enter MFGSTA under fields equal to 1. This limits the workflow firing those tracked and completed WO's.

Sorry now I'm done ! :D

thanks! I'm hoping to attempt this again tomorrow! I might drop a word doc of my documented steps if I'm not successful. Thanks to both of you for the help!