Illic 'a vulgaris negotium hujusmodi missionem:
- User implet quasi forma InfoPath.
- Forma suscipitur.
- Diu procul fluxum workflow processus amet.
- Dum currit workflow, Mutari nolimus quemquam formam dolor.
Hoc exemplum office.microsoft.com describes how to create a separate "view" and mark the whole view as read-only. This is a workable approach but has the drawback that you’ve effectively created two entire versions of the same form and must now keep them in sync manually. If you add a field to the editable view, you must then add it to the non-editable view as well. Super tempus, cum diversis tincidunt, there can be some divergence.
Vel hoc posset operari in quibusdam meliora:
- Add a new field to the form called "IsEditable".
- Verum pone eius defaltam ad valentiam.
- Promoveant cum publicantes MUSCUS.
- In workflow, statuet pretium IsEditble falsae.
- Revertere ad formam.
- Add a rule that "upon open of the form", disable vestri falsum est, nisi ipsum cum IsEditable.
The drawback to this approach is that all the fields will still be editable on the screen. The user can get a false impression that they can actually change content. You can mitigate that by putting in some text that the form is disabled, Page per litteras summum magnum rubrum possibile,.
Una project, I created a "workflow status" considerabit. As the workflow progressed, it would update specific status fields that had been promoted from the form. When the user opened the form, the "open form" regere automatically switched ut usura visum et habuit a nice status paulo summary.
</finem>
Et, you wrote "Pardon my ignorance, but when you refer to the "Save" button, are you referring to the button that appears on the top of the infopath form when displayed in Sharepoint, which I think is enabled in the "Open and Save Form options" when designing the form? Si ita, how can it be disabled by a rule – I’ve looked but must be missing something that is obvious. Gratias, Et"
In experientia, most "real" production forms end up having a specific button used to save the form. The default save function in InfoPath will prompt you for a file name and usually we want to generate that file name automatically. Ita, I mean to disable your custom submit button. HTH,
–Paulus Galvin
Pardon my ignorance, but when you refer to the "Save" button, are you referring to the button that appears on the top of the infopath form when displayed in Sharepoint, which I think is enabled in the "Open and Save Form options" when designing the form? Si ita, how can it be disabled by a rule – I’ve looked but must be missing something that is obvious. Gratias, Et
What happens in the scenario where you want to collect signatures for approval/denial as your workflow runs? If you disable the save – no further editing allowed – so if I’m looking at this correctly you got to leave the form editable to collect signatures = no solution.