Miriam, Is the form you're working with a customer facing form or for a service team? If a customer facing I'm not sure Task name = to would be valid, as you're not into any of the post ording moments. I would think using moment = ordering, alert, on load would be more appropriate.
If for someone past the customer/initiator I would actually try task name contains. We've not had that much luck with = to in our task name conditions.
Just my $0.02.
Miriam Rubin 5:29am, May 24
Thank you for your reply. Here's my situation. I have 1 ordering moment with 7 or 8 sub-tasks in them. Basically 7-8 players add information to the order before it can be submitted. So I'm not sure that moment = ordering would work, since all 7-8 are 'ordering moments' I want to use the AFC only for the first sub-task. I've tried 'contain's (upper/lower case) and have met with no luck. Any suggestions?
Ed Contini - newScale 6:59am, May 24
Miriam, If you name each one of your authorization/review tasks uniquely -- that is the Subject of the task, not the Name -- then your "Task Name > Contains" contitional rule will work. You can have your rule fire in the onLoad event, and you will be able to display a unique alert for each authorization/review task.
Just my $0.02.If for someone past the customer/initiator I would actually try task name contains. We've not had that much luck with = to in our task name conditions.Just my $0.02.