Security in CM 12.1 SP3

Question

Hi
Could you please share how are you handing following scenarios ?
We are using CM 12.1 (not immediate idea to upgrade 13)
Contractor, Project Management Consultant, Design Consultant, all have Edit privilege in Submittal.
All of them can change any dates
All of them can remove the attachment link
All of them can go and change the comments (we use remarks in Submittal revision)
Assume, we are not taking printout or scanning attaching to track the changes ?
Eventhough we are having some process to discipline etc, we can not prove if anything goes wrong. Since there is no proper audit trial (ya aware of the v13, version but not satisfied though fully)
Its bit weak in the security level.

Answer 1

Field-level security, in my own words:
Limiting access to a specific data field. Limiting access could be as restrictive as the user not seeing the field at all. Example: A Contract Manager RFI record has three primary areas of data entry, the Question, the Proposed Solution, and the Answer. I have been in situations where the owner refused to utilize the proposed Solution module because the Contractor could read its content. With field-level security the Contractor could be denied access to the Proposed Solution field; thhey wouldn't even know it exists. The Owner and Architect could then freely discuss the issue in the Proposed Solution field. The Contractor would still be able to view the Answer.
Additionally, record-level security would be nice to have. I'm not referring to Access by Company, either. I would like to see record edit and deletion privileges restricted to the record creator and/or super users/admins.
Selectable auditing, in my own words:
The ability to choose which modules and which records, and which fields and transactions within those modules and records are audited, and to what extent. Maybe I don't want full audtiting on every record. Maybe I only want it when a flag has been set regarding cost and/or follow-on work.
Many-to-many parallel, customizable workflows, in my own words:
Rigid, linear workflows are not realistic. Workflows can+ be simple, but more often than not they are very complex. I would like to be able to design a custom workflow for every business process where it's needed. The workflow capabilities of CM 12 and CM 13 are limited to specific modules and are purely linear, moving from one person to the next (someone from Oracle feel free to step in here and clarify if you disagree.) If you've seen Skire Unifier (or similar products) virtually every module can be created from scratch, without programming knowledge, and custom tailored to your specific business process needs. Granted, those systems usually cost more, and you get what you pay for. A many-to-many workflow, from my perspective, would be a situation where multiple people (in designated roles) could initiate a workflow that may be routed in parallel to multiple people simultaneously, for review and approval. Also, delegation for people on vacation or on sick leave would be part of the system, as well as the ability to set fiscal authority levels. Lastly, I would like to see the current Ball-In-Court functionality enhanced to support an organizational heirarchy. For example, I would like for a Construction Manager to be able to start at the Control Center screen and see his Action Items, as well as those of everyone who is underneath him in the organization (or project.)
While I'm the subject of many-to-many, I still desire the ability to link any document to any number of other documents without having to rely on the Issue builder.
As long as I'm ranting, I want program-level (or Group level) searching. I want module-selectable searching (like in the 8.x days.) I want to be able to specify the number of rows retrieved at the log level (25, 50, 100, ALL.) I want the ability to grant super-user delete privilege, with the ability to select multiple records for deletion AT THE LOG LEVEL. I want the option of enabling the old form view (non-tabbed view) within documents. I want the Next Record link (like in the 8.x days.) I want to hover over a field, or right-click, and see the table/view and field name.
Security in CM, in my own words:
Decent, but could be improved. For instance, let's say the Architect has the ability to Answer RFI's. This is great. The downside, unfortunately, will be revealed if you need custom fields for capturing additonal data. You often have to grant Edit privileges to the RFI module for the Architect (not necessarily Edit rights to the Question, but to the Answer and fields outside the Answer, because your custom fields may not be in the Answer portion of the form.) The Architect now has more privileges than we wanted in that scenario, partly due to the lack of field-level security.