Step 4: Balancing Resource Loads Across Projects
#Coupon code upgrade omniplan pro update#
An inactive project saves its repository account information, but loses the ability to publish or update until it is made active again. Active-tap to switch the project between active and inactive status.This is useful if the administration requirements of your project don’t involve gatekeeping of the changes made by others. Auto-Update Interval-tap to choose an interval at which the project will automatically receive new changes from the server.Repository-tap to select a different shared server for the project, manage repository accounts, or choose resource load publication settings.Once a project is published, a count of changes made since the previous publish action is displayed beneath the Publish and Update controls in the Project inspector.Īt any time after connecting a project to a shared server repository, tap Publish & Subscribe in the Project inspector to edit its repository settings. User-invoked publication and updates provide a mechanism for more deliberate information exchange and detailed change tracking tools for administration of the project.
This is by design-since the project is shared by multiple contributors, it’s important to monitor changes as they’re applied. Unlike OmniPlan’s OmniPresence sync and other cloud sync methods where the primary concern is keeping files in an identical state across your devices, publish and update actions don’t happen automatically when syncing to a shared repository. Until you tap Publish for the first time, the project continues to exist only locally on your device tapping Publish copies the project to the server for access by others. 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
#Coupon code upgrade omniplan pro pro#
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 kommentar(er)
