Duet 1.5 mostly comes with pre-packaged functionality in the form of scenarios. While there is implementation flexibility given with the Workflow template functionality, the other standard scenarios cannot be modified easily.
Of course, it is possible to perform personalization in the form of options given with each scenario. Additionally text labels can be adopted. However, if you require an additional parameter value to be sent to the SAP backend, it cannot be achieved with out-of-the-box development tools. Such modifications would typically mean a modification of Microsoft Office, which is not possible due to supportability reasons.
However, there are options for sending additional data to the backend from Duet.
In general, you can leverage the text field in Outlook with most scenarios, such as Leave Management, Sales Management, Time Management, etc., i.e. all scenarios where data from the text field is sent to the backend.
Some ABAP coding can be written and implemented onto the SAP system to pick up the information from the field once the data has arrived to the backend and use it for populating additional required information.
There might still be an issue with this approach though - lack of guidance and usability. While the approach is valid and works, the end user could write anything into the text field (it cannot easily be restricted from Outlook side). Additionally, an inexperienced Duet end user might not know what sort of data should be put into the text field.
There is a workaround to overcome this issue as well: make use of a form.
Let's assume your business process for creating a leave request requires one additional field to be maintained. You have modified the standard ESS leave request to cater for this requirement. To give an easy example, you might have to name a substitute for the period of your absence, which should be filled into the ECC system. To achieve this requirement from Duet side, we could put an additional link into the Duet Action Pane, which would open a form (works with different form technologies).
After having clicked the link the form would pop up, into which the user could enter all required values. Upon saving the form it can get attached to the email (which can be achieved by a simple Visual Basic script, for example).
In the subsequent step the leave request would be filled as in standard functionality. Upon sending the request, the form will be sent as well. The data can then be picked up again by means of ABAP coding as described in the previous approach.
