Welcome to the Sage X3 Support Group on Community Hub! Available 24/7, the Forums are a great place to ask and answer product questions, as well as share tips and tricks with Sage peers, partners, and pros from around the globe.
Hello, am wondering if someone can explain the logic behind Product Site Default Location setup? Problem: Snap shot above is how we are picking our apparel for replenish to work, but I don't think it's setup right 100%. Does anyone have any expierence…
Good afternoon!
I am looking to set up a new workflow rule which will automatically email all of the affected product-sites when a product status is changed.
So far, I have managed to set up a rule that will detect when the custom status field we…
Hi,
I'm trying to modify a standard workflow rule POHSIG to automatically sign PO if [F:POH]TOTORD < [F:POH]CREUSR maximum value
But it works only if user that creates PO is in the first line of Rule values.
For Example how it works in standard…
Below is a message I created for a workflow rule to notify end users they have an invoice ready for approval. Does anyone know why my "Total Cost" is not working? You can see it present in SQL with an amount and in the invoice.
|"Subject Invoice has…
I've created a separate signature workflow to the purchase signatures workflow. This is for new supplier setup requests.
Everything works great with signing the requests, but when the request is modified, the original signature request does not get…
Scenario:
User JOHN creates a new purchase request PR, on the signature user assignment he is the first to sign PR. After creating the PR, the PR is automatically signed.
I suppose this comes from the actions in the workflow that fires when the PR…
Hey folks,
I'm looking to resend a (ideally all) workflow notifications that have not been signed after a certain number of days. Is there a straightforward way in workflows that I'm missing?
Thanks!
Wondering if there are users that have found a way to exclude intersite transfers (Purchase order/Sales order) from purchase signature requirements. I've tried adding the BETFCY <> 2 in the workflow requirements, but am getting inconsistent results. Wondering…