Another question - does this apply to the email designer too?   Like if I want to add more fields to the workflow email then what is available?  

Question:    How does this work when there are multiple lines on the requisition?  I'm assuming it only looks at the first line and ignores all the others, so for customers who have people entering requisitions for multiple departments, it's only going to route based on the first account string, the rest will all just become a part of that routing rule right?  

This indeed worked perfectly, thanks for pointing out the more robust option to configure workflow. We linked the Vendor Master table to use Payment Priority.

I added an Extender item to the GP Req Entry Window. I can see my records in a SmartList.  The Workflow Conditioner Editor shows a bunch of Extender tables but not seem to have the table I am looking for. Can anyone point me in the right direction?

Efrain, yes it is possible to approve workflows from a device that is not connected to the domain. The email that is sent includes a hyperlink that calls into GP Web Services to process the workflow action. So you need to have GP Web Services deployed to an extranet that can be reached from the device. As long as that is set up correctly, you can do the workflow action from anywhere on the Internet.

In workflow for GP2015 is possible do the approval via email using mobile devices (not connected to the LAN)?

Haven't found information in the community and internet regarding it.

Found some article for Dynamics AX using in the infrastructure an 'Azure Bus'...

An update by MS support, dated April 13, 2016:

.  I did set the same workflow conditions per your screenshots that you provided and was able to produce the same error which indicates that you are correct in that it is only looking for tables within the same database.  They are looking at supporting this for GP 2016 when it is release but nothing has been decided or set in stone as of yet.

Hi there. This is great, however found when linking a System Table gets ODBC error, looks like it's working only with tables in same company, b/c system database is DYNAMICS (or the name given to the system database) internally is coding only the table name (without the database_name).

Second, the added fields only work for conditions, will be nice if can be also selected in the body of the messages.

George, any tables that are part of any dictionaries loaded with GP can be included in workflow conditions with these steps. Although we didn't specifically test with Extender tables, these should be included, as well.

Hello.  Would this process allow for eXtender table values to be added to workflow conditions as well?