Early next year we are removing certain outdated features from the Duco platform, as we now have better replacements to offer. To help guide those of you who may still be using them on proper next steps, please read the following suggestions.
Early next year we are going to sunset the following features:
- Manual actions without Exception Workflow enabled
- API versions 1&2
Manual actions without Exception Workflow
Update: As of January 2023 we have decided to postpone sunsetting of this feature to give our customers a bit more time to prepare for the change to Manual actions without Exception Workflow enabled. We will be sending further notifications before the change takes effect.
Although we have introduced a new Exception Workflow, some processes in your Duco environment may still use the older version with limited manual actions. This means that:
- At the moment you have only the match status buckets: Auto-matched, Partially matched, Unmatched. Sometimes you can also have additional buckets like Accepted, Filtered, Duplicates or Errors.
- Your status bar in the run overview, run history or on the processes page is showing the match status and not the Exception Workflow status.
- You have a limited list of available actions, including such actions as ‘Accept’, ‘Manually match’ etc.
At the moment, all the new processes are being created using this legacy workflow. Then the Exception Workflow needs to be enabled which provides more comprehensive functionalities to manage reconciliation exceptions.
What is changing
After the change all the new processes will be created without any Exception Workflow enabled. Also, those processes which will be left with the old workflow will be moved to no workflow setup early next year.
This means that:
- The match status buckets will still be available for iterative setup
- The run status bar will still be showing the match status of your records in the run
- The Actions menu in run results will not be available
- The Age, Comments and Labels columns will not be available in the run results and in the results export (manual export from the UI and export via API).
This will help you to concentrate on refining the process settings and getting the highest match score possible.
When your process is ready to go into production, enable Exception Workflow so that users can comment, label and perform manual actions on the exceptions.
If all your processes have the Exception Workflow enabled, you should not worry as there will be no changes for you.
- All the new processes will be created without any Exception Workflow, as described above. Once you are happy with the match results, you will be able to switch on the Exception Workflow. You may refer to a full guide on how to do it in this article.
If you have processes which don’t yet have the Exception Workflow enabled, you will need to make sure they are migrated to continue investigating the run results. You can refer to this Help Centre article for instructions on how to do this.
- During the migration some of the elements of the exception management workflow are changing (permissions, age calculation, etc). If you require additional support on the migration, reach out to your Customer Success Manager.
- If you are using the results export files from processes without the Exceptions Workflow as an input in other processes or reference tables, make sure you adjust the format of the input file in your process settings as the new columns will be added.
Our training team will organise the academy sessions which will go in detail through the upcoming changes and will be able to answer all the questions. Stay tuned for the new Duco Academy sessions.
The Cases feature was designed to help users investigate breaks. Since its inception, we have improved this ability by introducing the Exception Workflow.
What is changing
We will start with disabling the creation of new Cases. Then when we fully deprecate the feature, all existing cases will not be accessible. To assign reconciliation exceptions to users or groups, simply enable the Exception Workflow for your processes.
- The cases that are currently open will need to be closed by the time this feature gets switched off.
- The process settings have to be updated to use the new Exception Workflow to be able to investigate breaks. You can check this page for detailed instructions on how the Exception Workflow is working.
- If you are using cases to label the severity of a break, this can be achieved more effectively by using labels. For more information about best practice around labels, view this article.
The reports feature was designed to provide useful information about processes in the platform. With broader adoption of the product over the years, and being used in different businesses and scenarios, standard reports became less useful to users. We have since revolutionised our reporting capabilities through the Data Platform.
What is changing
Reports will be completely removed from Duco and the Reports page will no longer be available.
If you are viewing the reports page, we suggest you consider enabling the Data Platform to view more accurate and substantial information. For more details about Data Platform and its possibilities, view this article: What is available within the Duco Data Platform?
If you are interested in Data Platform, contact your Customer Success Manager or reach out to our Support team.
Currently, Duco has three API versions (1, 2, and 3) that may be used. If the version is not specified, Duco will default to choosing the second one when making calls. Currently, version 3 provides the best performance. Therefore, 1 and 2 will be removed early next year.
What is changing
The API versions 1&2 will not be available on the API page anymore and the calls made using the older versions will not be successful.
The default version will be changed from version 2 to version 3.
The Get/submissions API will have pagination in the newest version for improved performance.
All calls except Get/submissions:
- If you are specifying the version 1 or 2, you will need to change it to the version 3. If you do not update the version in your calls, after the migration they will fail with the ‘Page not found’ error message.
- If you are not specifying the version, the migration will be automatic.
- If you specify the version, you will need to change it to version 3 and update the call to make sure pagination is taken into consideration.
- If you do not specify the version, you will need to update the call to make sure pagination is taken into consideration.
For any questions related to these changes, feel free to contact our Support team.