You can now create a new mobile device control as an extension.
Here is how:
Create a class that extends WhsControl, and decorate the class with the WhsControlFactoryAttribute attribute specifying the name of your new control.
Naming considerations for the control name:
The name can be any string – prefix it with your organization’s name to avoid clashes.
Define it in your own macro. (For now class properties cannot be used as parameters to attributes).
- Implement the process() and populate() methods on your class. These methods should contain generic handling of the control. Use the members on the WhsControlContext to access and populate the captured fieldValues and other state of the current flow.
- If any flow specific handling is required, place it in the flow’s processControl() method. For this method to be invoked, the flow must call WhsRFControlData::processDataWithCallback() instead of WhsRFControlData::processData().
This diagram shows how you can plug in your flow – side-by-side with the existing controls:
Here is an example:
THIS POST APPLIES TO MICROSOFT DYNAMICS FOR OPERATIONS SPRING 2017 PREVIEW; IS PROVIDED AS-IS AND CONFERS NO RIGHTS.