They offer simplified features and behavior in order to take into account the widest spectrum of different actions.
When synchronizing with Outlook:
Refer to documentation Implementation
the information concerning a task are classified in the Task and Report tabs, but can be completed, modified or deleted.
Presentation
A task can be generated in three different ways in Sage X3:
The header screen is then used to identify a X3 task:
Close
Fields
The following fields are present on this tab :
Block number 2
Block number 1
| This field specifies the site on which the task in question is mainly managed. Several setups intervene in the default site preloading. It can be the site linked with the profile function of the current user or the site linked with the Sales rep in charge of the commercial action (CRMREPSIT setup, CRM chapter, REP group). |
| This field is used to store the unique key for the record. This key is calculated by the ACT sequence number counter. By default, this counter is made up of a sequence number made up of 15 characters. This counter is provided as standard with an automatic operation, but its allocation can be manually performed. To ensure the correct functioning of the Task object, it is strongly advised to conserve these standard characteristics. The ACT sequence number counter is shared by the Tasks, Appointments, Calls and Actions objects. Indeed, this is used to exploit the functionality and the Crystal Report reports working with the notion of commercial activity in its broadest sense. |
| It is possible to identify a task for all the different business partner types. A field displayed with regard to the BPs makes it possible to know the BP type selected. |
| This field is used to identify either a default contact from the BP concerned (modifiable field), or a contact for whom the task must be carried out in the case where no BP is identified. Several contact selection tools are available from this field: The first "selection" contextual menu is used to select a contact among a contact list irrespective of the BP code mentioned in the task header. The second "Select contacts" contextual menu is used to select a contact among the list of existing contacts also linked with the BP entered in the header. If no contact has been assigned to the BP, no contacts selection list is displayed. The third contextual menu "Contacts selection" is used to select a contact the complete list of all the contacts entered in the application. |
| Reminder of the contact's full identity entered in the task header. |
| A task can be attached to a corresponding chrono (issue). This chrono can be selected manually, directly from the field or pre-loaded depending on the contact chrono previously entered in the task header. |
| This field is used to identify the project for which the task must be carried out. Various selection tools of a project are available from this field. The second contextual menu "Project" allows the direct access the Projects object and to carry out a specific selection. The second contextual menu is used to select a project among the list of all the project linked with the BP entered in the task header. The third contextual menu is used to select a project among the list of all the project linked with the contact entered in the task header. |
| This field transforms the status of the tasks from "To do" to "Done". This modification mainly leads to the disappearance of the task from the sales representative's workbench. |
Close
Presentation
The Task tab is used to enter more detailed information on the current task, as well as its sequence (task triggering event, description of stages...). Temporal information can be added (start date, due date, delay)
From this screen, it is possible to enter a task successive and detailed description.
In the same way, the origin of a task is expected to change in time. To do so, it is possible to unlock by right-clicking on the Link field (triggering event), then by selecting an event type and a specific record.
Notes on a task's origin:
This link field of the section "Origin" displays the action at the origin of the task creation. The origin of a task can be a service request (assignment of the service request to a commercial department), a marketing campaign, especially a marketing operation (mailing, call campaign, trade shows or media campaign), an Outlook task synchronization. The origin of a task can also be manual (direct creation from the Task object).
Irrespective of the task' origin, it is still possible to unlock a posteriori the field from the contextual menu available by a right-click. Once the field can be accessed in entry, the user can modify the origin (values selection from a check list). For instance, attaching a project to a marketing campaign is used to feed the return statistics.
Every task created in Outlook, then generated in Sage X3 following the launch of the synchronization processing, implies that the origin will take the value "synchronization". This is true on the condition that the synchronization parameters allow it (parameters CRMSYNC -Synchronization Management, CRMSYNCTSK - tasks synchro management, and Synchronization function).
Close
Fields
The following fields are present on this tab :
Block number 4
Planning
| This field contains the date from which the task must appear in the workbench of the sales representative concerned. This field is also set by default to the current date during the creation of a new task. |
| This field contains the date for which the task must be carried out. During the creation of a new task, this date is automatically defined as the current date +1. |
| The category is used to group the tasks for statistical or identification purposes. Entering this field is not mandatory, but the possible values are controlled in the 431 miscellaneous table. |
| This field specifies the priority assigned to the task. Entering this field is not mandatory, but the possible values are controlled in the 405 miscellaneous table. |
| This field contains the name of the sales representative who must carry out the requested task. Several setups intervene when loading this field:
|
| This field is used to enter the number of days late above which the requester would like to be informed in their workbench of the non execution of the task in date and time. |
Description
| This field, of Clob type, is used to enter a description of the task. |
Source
| Current date at which the CRM activity has been created. This information cannot be modified. |
| Current time at which the CRM activity has been created. This information cannot be modified. |
|   |
| This is the code for the current user which is responsible for the creation of the CRM activity. This information cannot be modified. |
|   |
| When a task originates from a service request, a maketing campaign or a marketing operation, this field displays the most exactly linked record number. |
| When a task originates from a service request, a marketing campaign or a marketing operation, the number of the original document is displayed but a line number in the recording can also be associated. |
Close
Action icon
Presentation
The Report tab is used to enter conclusion comments on a task, but also to value the time spent on the current task.
Fields
The following fields are present on this tab :
Report
| This field, of Clob type, is used to enter a compete report on the task once it is accomplished. |
|   |
Time spent
| When the task is completed, it is recommended to indicate the time taken to complete it. |
| This field specifies the time unit in which the task is expressed. |
| When the task is completed, it is recommended to indicate the time taken to complete it. |
| This field specifies the time unit in which the task is expressed. |
| When a commercial action is completed, it is recommended to record if the objective has been reached. This information can the be used later to establish the statistics to help with the progressive improvement of the different teams efficiency |
By default, the following reports are associated with this function :
BUSINESS1 : Sales activities/date
BUSINESS2 : Sales activity/sales rep
This can be changed using a different setup.
The "Actions/Plan/Appointment" menu in the tool bar is used to create an appointment directly in the "Appointments" function.
The "Actions/Plan/Call" menu in the tool bar is used to create a call directly in the "Call" function.
The "Actions/Save/Appointment" menu in the tool bar is used to create an appointment directly in the "Appointments" function.
The "Actions/Save/Call" menu in the tool bar is used to create a call directly in the "Call" function.
The "Actions/Save/Project" menu in the tool bar is used to create a project directly in the "Projects" function.
The "Actions/Save/Service request" menu in the tool bar is used to create a call directly in the "Service Request" function.
This option gives access, via a tunnel, to the Journal traceability inquiry function that makes it possible to view and browse the hierarchy of the entries originating the document or coming from it.
In addition to the generic error messages, the following messages can appear during the entry :
This message is displayed if no representative has been entered for the task and the automatic assignment has failed on creating the task.
This message is displayed when confirming the modification of a task. No representative has been entered for the task and the automatic assignment of the task has failed.