Rule - Save order number as the project number
Organizations sometimes take on large projects that need to be tracked and traced at every step. Often the best way to do that is to assign a tracking number of some kind (maybe you call it a contract ID or a project #) to the entire process and make sure that every transaction associated with the project includes that number.
Let's talk about the setup required to properly install and run a rule that will automatically save the sales order number as the project number. That number can then be transferred or inherited to every transaction that is linked to that order.
Step 1 - Create the project number attribute
In this example, we've named the attribute Contract Number. It must be a free flow text type attribute.
Step 2 - Add project number to transaction screen setup
We will have to add our new attribute Contract Number to the more tab of the order via screen setup. If you would like to have this attribute filled on any transaction created from the orders, add it to those screens as well.
Step 3 - Add project number to transaction inheritance
If in fact you need this attribute to copy to any transactions created from orders, set up attribute inheritance accordingly. If this is not one of your requirements, skip to Step 4.
In this example, we have determined that our attribute Contract Number will be inherited from orders to purchase orders.
Step 4 - Install and run the rule
Here we have named the rule save order number as the project number and applied it to the after_save_order trigger. We imported the rule and changed it to properly use our attribute Contract Number. We then activated the rule so it is set to run the next time we save an order.
Step 5 - Create an order and trigger the rule
For our example, we created a simple order and saved it. We received a notification telling us that the attribute has been filled.
If the required setup has been done, any transaction created from this order will automatically inherit the Contract Number:
What's next?
Now that your rule has been installed and is working, you can always deactivate it if you need to. Need help setting up rules? Contact us at support@paragon-erp.com
Related Articles
Rule - How to set up pricing by quantity
For some products, depending on industry practices, customer contracts, or other purposes, you might want to calculate and indicate the total price for a certain quantity of your product. For example, if you always sell a product by thousands, it ...Rule - Sales order to automated receipts workflow
Project management can be facilitated by automation rules that will help to reduce some of your manual tasks. In this example, we will address the requirement to generate shipment receipts within a workflow that does not have physical shipments into ...Rule - Create a work order automatically from an order
Does your manufacturing workflow involve creating work orders? Do you aggregate items from different orders to create a cumulative work order? We understand how painful it could be to do this manually. That's why we have built the option for you to ...How to create a freeflow text or number entry attribute
The following document will explain how to enter free flow or entry attributes in Paragon. Find out more about what attributes are and how they can be used. Here, we'll walk you through how to create free flow or free entry text and number ...How to add options to the payment type attribute
ParagonERP comes standard with certain attributes; one of which is the payment type attribute. This attribute is mandatory on the receive payment and make payment modules. In this article, we'll show you how to add payment types to your payment ...