All bindings should not populate in the workflows if those are not part of Form
Presently binding those are not part of form are also populating with in Status (Enable and disable properties boxes). I understand that bindings are company/projectwide. If I am having 50 forms per project, in this case it's really difficult to f...
Sachin Sharma
about 4 years ago
in SYNCHRO Control / Forms
0
Future consideration
Add Contingency Transfer (CT) to contract (similar to Change Order)
CT is a line item in the SOV that is already funded and is used to cover the cost for unforseen conditions. This is not added to the contract or SOV as it is already a line item but the CT would document the use of these funds.
Allow different SYNCHRO Forms permissions to be set at various workflow states
Currently, we can assign each user role a set of permissions (e.g. View, Create and Edit, Assign). With role-based access control, for each user, we can restrict access to workflow state changes of forms and form visibility. However, this is still...
Ability to map field to more than one PDF location
Control only allows each field to map to one spot on a PDF. There are many fields were the information needs to be mapped to different locations on the PDF - like when each pdf page has data in the header. The Forms service has no limitation.... i...
This idea refers to using Synchro Control with an iModel with Projectwise Connections. When viewing the Connections I think it is essential to be able to see the version of the model, e.g. P03 or C06. The model version isn't listed on the Connecti...
0
Future consideration
2
Future consideration
0
Future consideration
