Skip to main content

Publication plan

The Publication Plan (mvn__PP_Plan__c) custom object is the primary object that facilitates publications planning and the coordination of plan-related activities. Child Annual Plan (mvn__PP_Plan_Budget__c) records manage the budget for the publication plan and help track Line Item (mvn__PP_Plan_Budget_Line_Item__c) and Line Item Payment (mvn__PP_Line_Item_Payment__c) records.

Both Concept (mvn__PP_Concept__c) records and Document (mvn__CM_Document__c) records can be related to publication plans as well. Concepts are user-submitted publication ideas related to a product and/or study. You can convert or reject these requests. Documents are the fundamental files for publication plans. You can view the milestone deadlines for the related documents and their targets in the Timeline (ppTimelineWrapper) component.

Timeline

Publication plan timeline filter

You can filter a publication plan's timeline to make it easier to review specific publication plan attributes.

To use these filters on a Publication Plan record:

  1. Click the Timeline tab.

  2. Click the Filter (Filter icon) icon on the right-hand side.

  3. Select the desired criteria from the dropdown lists attached to the filter options. Filter options include:

    • Year

    • Document Type

    • Document Subtype

    • Document Classification

    • Study

    • Congress

    • Journal

  4. Click Apply Filters.

To clear previously selected filters, either click the Filter icon and then Clear Filters or click the Refresh (refresh icon) icon to the left of the Filter icon.

Plan team members

Users who are part of the planning team are referred to as plan team members and are managed in the Plan Team Member (mvn__PP_Plan_Team_Member__c) custom object. Each Plan Team Member record can be related to a Publication Plan record, and each plan team member can have a designated role on the publication plan. The picklist values in the Role (mvn__PP_Role__c) field are the available roles that you can assign to a plan team member when adding them to a publication plan. The selected role will determine the permissions that the plan team member has on the publication plan, including any newly added documents. To grant a plan team member access to existing documents on the publication plan, you must assign an Existing Role (mvn__PP_Existing_Role__c) value on the Plan Team Member record as well. There can only be one plan team member with the plan owner role on any publication plan.

Note

For plan team members to automatically be provisioned access to a document when the document is related to a plan, the following must be true:

  • The API name of the Document Type (CM_Latest_Version_Type__c) value on the Document record must match the Publication Document Criteria (mvn__PP_Publication_Document_Criteria__c) value on the Default (PP_Default) metadata record of the Pubs Global Setting (mvn__PP_Global_Setting__mdt) custom metadata type.

  • The API names of the Role picklist values must match the Name (DeveloperName) values of Role (mvn__CM_Role__mdt) custom metadata records.

When both of the above are true, plan team members are added as document collaborators and provisioned with the corresponding role and permissions configured for the document lifecycle.