Difference between revisions of "How to Process System Events (General Instructions)"

From crazysales
Jump to: navigation, search
Line 1: Line 1:
  
  
'''System events''' are system generated events corresponding to orders with different issues. Some system events will prevent orders to be sent out and others will not. These system events are classified in different types and need different procedures. These classifications are called as “Event Types”.  
+
'''System events''' are system generated events corresponding to orders with different issues. Some system events will prevent orders to be sent out and others will not. These system events are classified in different types and need different [http://106.75.199.24/mediawiki/index.php?title=System_Events_AU procedures]. These classifications are called as “Event Types”.  
  
  

Revision as of 10:14, 23 March 2017


System events are system generated events corresponding to orders with different issues. Some system events will prevent orders to be sent out and others will not. These system events are classified in different types and need different procedures. These classifications are called as “Event Types”.


To go to the system events, please follow the steps below:

  • Step 1. Go to: Crazysales Backend
  • Step 2: Click on “Customers and Orders”.
  • Step 3: Click on “System Events”.
    Wb1b.png




Things to remember:

  • a. Make sure you are in the "To Process" page which means that the system events are not yet done.
  • b. Click on “Show All” to view all system events.
  • c. Click on the arrow up to show the system events in an ascending order.


    Wb2.jpg




To do a certain system event, please follow the steps below:

  • Step 1: Control click “here”:
   Wb3.jpg

  • Step 2: Based on the kind of event, provide/edit needed information.
  • Step 3: Add note about what you have done in a certain order.
  • Step 4: Check/change order status if needed.
  • Step 5: Click “Finish” only if the system event is solved. If not, place a remark as reference by clicking “Remark” and “Save”.


Editor/s:

Willy Balanoyos; Jane Jian