Pamper your customers and colleagues!
The standard Profit views have been optimised by using the knowledge gained down the years. New ones have also been added. User friendliness, efficiency, speed and best business practices were examined within this context. Views in InSite and OutSite have not been changed.
New views
For example, new views have been added that previously had only been included in the templates. These are now available to everyone! Sometimes, new and existing views have been renumbered and therefore the most important views will be at the front automatically (left).
Below you will find a new view in Financial / Ledger / Financial entries as an example. You will only see the entries for the last year.
Every function will open as standard with a specific preferred view. It may be the case now that a function opens with another view as standard because of the changes and the new views.
Note:
If you authorise views separately via the definition authorisation, new views will not be displayed immediately. You must first link the correct Definition category or group to these views.
Adjusted views
Existing views have been checked and expanded and/or changed where required. Some existing views now have a different name so that they are consistent with the new ones. A frequently occurring change is the replacement of the First name field by Nickname.
Adjusted views are not delivered unblocked. You must unblock the view yourself to benefit from this.
Deleted views
Double views or views that do not have added value when compared to other views were also critically examined (this is not an exhaustive list). Views have also been deleted because of this. If you made analyses on these views, you must make them again.
It may be the case that you see a Profit view and a very similar template view because the template views are now in Profit. These template views are not deleted automatically. You can do this yourself.
More options with import
Every import wizard now has the Check whether file was imported before (based on content) field. This ensures that you can, for example, prevent that claim lines are imported twice by accident.
If you try to import a file for a second time, you will immediately receive a warning. This will also happen if a previous import action failed.
The Check whether file was imported before (based on content) field will be selected by default because it obvious that the user would always want to perform this check. You can deselect this field when testing an import, of course, in a test environment.
You can consult the history of the performed imports via General / Management / Import / History (do not forget to authorise this function). This function will log both successful and failed imports.
You can also retrieve this data with a GetConnector based on the Import history and Import history lines data collections.
As from Profit 7, you can use more letters with accents in names of persons (employees), organisations and city and town names. This ensures, for example, that you can also record the names of employees from Eastern Europe correctly in Profit.
This is now also possible via the import. You can now therefore also import names with the characters from the adjacent figure.
If you've installed the PCC, a PDF will always be opened on your local system using the locally installed PDF application.
If you haven't installed the PCC, the PDF will now be opened in the AFAS PDF viewer on AFAS Online. From the PDF viewer it's possible to save the PDF to a local folder.
The PDF will be opened with the PDF program on your own computer if you have an on premisys Profit-installation.
There is no new PCC for Profit 8. You can continue to use the last released PCC for Profit 7.
in Profit 7, you can use an email message based on a template, to send an a-mail based on an alert. This allows you for each alert, to use a customised e-mail template with graphics and data (fields) from the alert. As from Profit 8, you can also save these emails in the dossier of the organisation or person.
You enable this in the alert's destination. Of course, the alert should be sent by email. If you enable the Save the sent email in the file of the person or organisation field, then when the alert is generated, the email will be sent and it will be saved in the destinations dossier (as a dossier item with the original email message as an attachment).
In this example, you see an alert with an mail message about an outstanding item that is overdue. The email message will be saved as a dossier item with the organisation, so you have central access to all communication with the organisation (administratie@enyoi.com is the business email address).
The following fields have been added to these UpdateConnectors. You can enter date in these fields when adding an employee. If you do not enter data for these fields, the value will be automatically determined.
If you deliver an article to multiple sales contacts, you can define deviating data for each sales contact such as the item code and barcode of the sales contact, the ordering unit, etc. You can now also add this data using this new UpdateConnector.
Via the UpdateConnector for receipt (FbGoodsReceived), you can now specify location lines at the level of the receipt line, batch line and serial number line. Use the FbOrderLocationLines element for this.
The UpdateConnector returns the project number in the PrId field in the response in relation to a new project.
When submitting and updating actual costing lines, the ID of the actual costing line, the external IK and the SessionGuid are returned. The <XpRe> tag can also be entered using the ID of the external application via XML or JSON.
You can now create an actual costing line based on the sales contact item code that has been defined on the Items of the sales contact tab via the UpdateConnector PtRealization. When executing the actual costing line, both the sales contact item code and the sales contact number must be entered in the import as XML. Next, the internal Profit item code will be searched for.
You can get the dates of the changed actual costing lines with the GetConnector Profit_Rea_ChangedEntryDate (Gewijzigde_boekingsdagen_nacalculatie data set).
You can retrieve the dates of changed actual costing lines in a targeted manner with this. Next, use a GetConnector for actual costing lines to retrieve the changed lines as such.
The fields of the Record 281.50 tab were not available in the UpdateConnector. The following fields are now available:
You can consult the authorised users for each menu choice, tab, authorisation filter or action in the Authorisation tool.
Now, you can also create a report, analysis or GetConnector with this data with the new User processes (report) data set. You can also quickly see whether specific authorisation has been given on a user level instead of on a user group level via this data set. See the adjacent example.
A username in AFAS Online always consists of your participant number and number in AFAS, for example, 12345.MartinW. The maximum length of the code has been increased from 20 to 64 characters.
User actions are often logged in Profit. This, for example, means that when a data item has been changed, who implemented the change will be logged.
The logging on users will not be deleted when users are deleted. You can delete the logging of deleted user via the new General / Management / Personal data / Update logging fields function. This will convert the relevant usernames in the AFASUSER name.
Do not forget to authorise the General / Management / Personal data / Update logging fields function.