![]() Once you’ve chosen a server repository for your shared project, options to Publish changes to the project and Update the project based on changes made remotely appear in the project’s Project inspector. Step 3: Publishing and Subscribing to Project Changes If either of these scenarios apply to your project, the publication and subscription features of OmniPlan Pro repository sync are just what you need. Likewise, if resources are shared between multiple projects simultaneously (staff working on Phase 1 of Project Alpha and Phase 3 of Project Beta concurrently), storing projects in the same repository allows resources with the same unique identifier to be leveled intelligently across all projects that include them. When stored in a shared server repository, multiple users can publish and subscribe to changes to a project, and the project’s administrator can review and accept or reject each change as it is made. ![]() If a project has multiple editors-staff who update their own task completion percentages and extra hours worked, or site managers who track resource costs, for example-the need for collaborative features becomes evident. If the project is administrated, edited, and updated primarily by a single individual, and resources relevant to the project are exclusive to that project (among projects administrated simultaneously by the user), the standard edition of OmniPlan offers OmniPresence sync as a solution that meets most needs. ![]() Whether OmniPlan’s collaborative syncing features are appropriate for your project depends on a few factors. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |