Classification: For internal use only Kerry,
The trouble you will have is when to fire the check. If you want to capture the users that had a Floating Lic but have now got a Read Floater (due to timeout etc), you will need to fire the workflow before every transaction unless you only wish to track those users who are given a read floater on login. If that is the case, you could fire workflow on login that sets a hidden field and commits. If they have a Floater the commit will save the checkbox etc... if they have a read it wont. You can then use that checkbox in your check qualification. Regards, Paul --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
