Job - Synchronize Page Model and Pagelet Instances

Personal Library

Name	Synchronize Page Model and Pagelet Instances
Domain	SLDSystem
Job Dependencies	none
AcquiredResources	none
Cartridge	sld_system_app
Pipeline	SynchronizePages-Start
Affected Domain Objects	View Contexts Pages Includes Page Variants Components Page Templates Component Templates
Affected Tables	CONFIGURATIONPARAMETERVIEWCONTEXT VIEWCONTEXT_AV VIEWCONTEXT_PEPA PAGELET PAGELET_AV PAGELETCONSTRAINT PAGELETCONSTRAINTCTNR PAGELETDEFINITIONCONSTRAINT PAGELETENTRYPOINT PAGELETENTRYPOINT_PCCA PAGELETENTRYPOINT_AV PAGELETENTRYPOINTLABELASSIGNMT PAGELETENTRYPOINTRELATION PAGELETENTRYPOINTSHARINGINFO PAGELETENTRYPOINT_PA PAGELETLABELASSIGNMENT PLACEHOLDERDEF PLACEHOLDERDEF_AV PLACEHOLDERDEF_PCCA PLACEHOLDER_PA PLACEHOLDER_PARENT PLACEHOLDER_PARENT_AV PLACEHOLDER_PPA PLACEHOLDER_PPA_AV PLACEHOLDER_SPA PLACEHOLDER_SPA_AV SLOT SLOT_AV SLOTPAGELETASSIGNMENT SLOTSHARINGINFO USERGROUP_PA PRODUCT_PEPA CATALOGCATEGORY_PEPA ABTESTGROUP_PA
Stored Procedure	None
Default State	Disabled
Is Site Specific	False
Edit State	Globally Enabled
Live State	Globally Enabled
Server Group	JOB
Description	This job synchronizes all existing content instances with the current content model: All content instances referring to nonexistent content models will be removed. This includes dependent content instances too. For each new content model element whose type declares a system managed flag and this flag is set to true, a system-managed content instance will be created within each content repository where the content model element is visible. The inner structure of content instances will be updated when there are items missing according to the respective content model. Right now, this affects only the slots of pagelets. Relations between content instances are checked for validity according to the content model and otherwise deleted.
Scheduling	This job must never be used in a production environment. It may lead to severe data loss and is meant only to support a content developer who has to deal with a lot of content model changes by preventing invalid content instances according to the content model.
What Happens Switched Off	This job is there to ease CMS development efforts. It is only meant to be used in edit or development environments. Pagelet, ViewContext, Slot, PageletEntryPoint or other CMS objects whose defining Pagelet Model files (.pagelet2) have been changed will become outdated/invalid. If this job is not executed, these outdated or invalid objects will remain.
Trouble Shooting	None
Comments

Product Version	7.0
Product To Version
Status	New Labels

Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.