Orders - Revision history

Pinvoicer at 06:19, 20 August 2019

2019-08-20T06:19:41Z

Pinvoicer: /* Clear Old Orders */

2019-07-04T22:46:35Z

Clear Old Orders

Pinvoicer: /* Clear Old Orders */

2019-07-04T22:46:06Z

Clear Old Orders

Pinvoicer: /* Clear Old Orders */

2019-07-04T22:45:43Z

Clear Old Orders

Pinvoicer: /* Clear Old Orders */

2019-07-04T22:45:15Z

Clear Old Orders

Pinvoicer: /* Clear Old Orders */

2019-07-04T22:43:44Z

Clear Old Orders

Pinvoicer at 22:42, 4 July 2019

2019-07-04T22:42:50Z

Pinvoicer at 22:41, 4 July 2019

2019-07-04T22:41:35Z

Pinvoicer at 22:40, 4 July 2019

2019-07-04T22:40:59Z

Pinvoicer at 06:27, 28 May 2019

2019-05-28T06:27:50Z

← Older revision		Revision as of 06:19, 20 August 2019
Line 24:		Line 24:


−	[[File:add-order.jpg]]	+	[[File:add-order.jpg\|800px]]


Line 44:		Line 44:


−	[[File:filter_order.jpg]]	+	[[File:filter_order.jpg\|800px]]

@@ Line 66: / Line 66: @@
 Example: For week ending 30th June you'd need to do this;
-* In RecruitOnline - make sure that any orders that were not current for the week ending 30th June have been closed and the finish date when closing set to a date on or before 24th June (ie w/e 30th June will be all orders that are in 24th to 30th June).
+* '''In RecruitOnline''' - make sure that any orders that were not current for the week ending 30th June have been closed and the finish date when closing set to a date on or before 24th June (ie w/e 30th June will be all orders that are in 24th to 30th June).
-* In RecruitOnline - make sure you have used the PinvoiceR Export to get the orders across - ie if you have updated an order with a new finish date - the only way PinvoiceR will know is to have the ROL > PinvoiceR Export done again.
+* '''In RecruitOnline''' - make sure you have used the PinvoiceR Export to get the orders across - ie if you have updated an order with a new finish date - the only way PinvoiceR will know is to have the ROL > PinvoiceR Export done again.
-* In PinvoiceR - click the <kbd>Clear Old Orders</kbd> button on the orders screen - this is set to clear all orders that finish 7 days before the week ending you are in (ie 30th processing will clear all orders from 23rd June and before).
+* '''In PinvoiceR''' - click the <kbd>Clear Old Orders</kbd> button on the orders screen - this is set to clear all orders that finish 7 days before the week ending you are in (ie 30th processing will clear all orders from 23rd June and before).
 For info - there is a setting for both weekly and daily orders in the Entity Editor that sets the number of days that the clear old orders button spans - this is defaulted to 7 days but you can adjust accordingly.

@@ Line 62: / Line 62: @@
 PinvoiceR does not automatically clear old orders from the orders screen as in many instances we have found that having the system do this tends to cause more issues as people invariably forget to update orders in RecruitOnline and this can cause issues when orders are automatically closed.
-So the way that it is handled in PinvoiceR is to use the <kbd>Clear Old Orders</kbd button on the Orders screen. The following is an example of what you would need to have have happen in ROL/PinvoiceR for this process to work effectively;
+So the way that it is handled in PinvoiceR is to use the <kbd>Clear Old Orders</kbd> button on the Orders screen. The following is an example of what you would need to have have happen in ROL/PinvoiceR for this process to work effectively;
 Example: For week ending 30th June you'd need to do this;
 * In RecruitOnline - make sure that any orders that were not current for the week ending 30th June have been closed and the finish date when closing set to a date on or before 24th June (ie w/e 30th June will be all orders that are in 24th to 30th June).
 ==Related Pages==

← Older revision		Revision as of 22:45, 4 July 2019
Line 67:		Line 67:

	* In RecruitOnline - make sure that any orders that were not current for the week ending 30th June have been closed and the finish date when closing set to a date on or before 24th June (ie w/e 30th June will be all orders that are in 24th to 30th June).		* In RecruitOnline - make sure that any orders that were not current for the week ending 30th June have been closed and the finish date when closing set to a date on or before 24th June (ie w/e 30th June will be all orders that are in 24th to 30th June).
−
−	* In RecruitOnline - make sure you have used the PinvoiceR Export to get the orders across - ie if you have updated an order with a new finish date - the only way PinvoiceR will know is to have the ROL > PinvoiceR Export done again.
−
−	* In PinvoiceR - click the <kbd>Clear Old Orders</kbd> button on the orders screen - this is set to clear all orders that finish 7 days before the week ending you are in (ie 30th processing will clear all orders from 23rd June and before).
−
−	For info - there is a setting for both weekly and daily orders in the Entity Editor that sets the number of days that the clear old orders button spans - this is defaulted to 7 days but you can adjust accordingly.

	==Related Pages==		==Related Pages==

@@ Line 64: / Line 64: @@
 So the way that it is handled in PinvoiceR is to use the <kbd>Clear Old Orders</kbd button on the Orders screen. The following is an example of what you would need to have have happen in ROL/PinvoiceR for this process to work effectively;
 Example: For week ending 30th June you'd need to do this;
 * In RecruitOnline - make sure that any orders that were not current for the week ending 30th June have been closed and the finish date when closing set to a date on or before 24th June (ie w/e 30th June will be all orders that are in 24th to 30th June).

← Older revision		Revision as of 22:40, 4 July 2019
Line 56:		Line 56:

	From the Orders screen, click on the pencil icon in the row of the order that you want to edit.		From the Orders screen, click on the pencil icon in the row of the order that you want to edit.
		+
		+
		+	==Clear Old Orders==
		+
		+	PinvoiceR does not automatically clear old orders from the orders screen as in many instances we have found that having the system do this tends to cause more issues as people invariably forget to update orders in RecruitOnline and this can cause issues when orders are automatically closed.
		+
		+	So the way that it is handled in PinvoiceR is to use the <kbd>Clear Old Orders</kbd button on the Orders screen. The following is an example of what you would need to have have happen in ROL/PinvoiceR for this process to work effectively;
		+
		+	Example: For week ending 30th June you'd need to do this;
		+
		+	* In ROL - make sure that any orders that were not current for the week ending 30th June have been closed and the finish date when closing set to a date on or before 24th June (ie w/e 30th June will be all orders that are in 24th to 30th June).
		+	* In ROL - make sure you have used the PinvoiceR.Export to get the orders across - ie if you have updated an order with a new finish date - the only way PinvoiceR will know is to have the ROL > PinvoiceR Export done again
		+	* In PinvoiceR - click the <kbd>Clear Old Orders</kbd> button on the orders screen - this is set to clear all orders that finish 7 days before the week ending you are in (ie 30th processing will clear all orders from 23rd June and before).
		+
		+	For info - there is a setting for both weekly and daily orders in the Entity Editor that sets the number of days that the clear old orders button spans - this is defaulted to 7 days but you can adjust accordingly.
		+
		+

	==Related Pages==		==Related Pages==

@@ Line 19: / Line 19: @@
 == How to Add an Order ==
-Most orders will flow through automatically from the front end system (such as RecruitOnline, RDB etc) and they are managed by the order process in that system.
+Most orders will flow through automatically from the front end system (such as RecruitOnline) and they are managed by the order process in that system.
 In instances where you wish to manually add orders in PinvoiceR - click on Payroll > Orders and then click on the <kbd>Add Order</kbd> button;