Time to time I will be adding some tips on how to use Agresso from the user's point of view but there will also be some tips valued by a System Administrator. Some of the images used here are from different versions of the system.
Tips for a System Admin
Get link
Facebook
X
Pinterest
Email
Other Apps
Time to time I will be sharing some tips about what can help a system admin on their work or their environment and mindset.
"We make a living by what we get, but we make a life by what we give" - Winston Churchill
Before contacting your Agresso team for information on how to terminate your own requisition please try this guide below: Go to Procurement Then Requisition Standard Press the Open button Type your Requisition Number Once you tab out of the field it should show your requisition again (if it has not been approved in the workflow already) Now change the status from Active to Close and Save it. PS: If you want to close your requisition but it is already in the workflow waiting for approval ask the approver to reject your requisition so it can go back to you and then you can change the status to Close . If you want to know who is holding back your requisition in the workflow check my post: "How to check your requisition status" .
On some versions of Unit4, such as 7.3, the error message “Position Illegal” can come up when a manager is trying to amend an existing absence for their staff. This error is normally displayed when they have re-opened the existing absence by filtering only by the employee’s Res ID. In this case, they will also need to fill in the containing date field to be able to save any amendments on that existing absence.
You might need this information for different reasons, one of them could be when you are closing or parking some users accounts which are not being in use anymore. To check when was the last time they've used their Unit4 account follow the steps below: Go to Settings - Then System Administration - System Access Log. (Screenshot 1) Double click on it and insert the res ID for the user field. (Screenshot 2)