{"id":1729,"date":"2020-03-14T22:00:53","date_gmt":"2020-03-15T02:00:53","guid":{"rendered":"https:\/\/www.foxquestsystems.net\/foxblog\/?p=1729"},"modified":"2020-03-14T22:00:59","modified_gmt":"2020-03-15T02:00:59","slug":"reporting-changed-logic-to-existing-activities","status":"publish","type":"post","link":"https:\/\/www.foxquestsystems.net\/foxblog\/2020\/03\/14\/reporting-changed-logic-to-existing-activities\/","title":{"rendered":"Reporting Changed Logic to Existing Activities"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Tracking logic changes can be a nightmare,\nespecially when it comes to large CPM networks with ever changing scope and\nconditions. Many schedule specifications require that for each logic change, a\ndescription for the basis of each change is provided and specifically\nidentifying the affected activities by Activity ID. In other words, the Owner\nis not just interested in what changed, but more so, why the change was made.\nMaking matters worse, typically each change requires an individual explanation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Comparison Report: <br><strong>Changed Logic To Existing Activities<\/strong> \u2013 shown below groups predecessor logic changes by Activity ID. The action taken, Added or Deleted Predecessor, is coded as AP or DP. The report also displays the Activity Name, Relationship, Lag and Total Float values. The advantage of this report is that all relationship changes including Predecessors and Successors whether deleted or added for any particular Activity ID is consolidate in one place.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large is-resized\"><img data-recalc-dims=\"1\" decoding=\"async\" loading=\"lazy\" src=\"https:\/\/i0.wp.com\/www.foxquestsystems.net\/foxblog\/wp-content\/uploads\/2020\/03\/T499-Changed-Logic-To-Existing-Activities-Screenshot.jpg?resize=840%2C371&#038;ssl=1\" alt=\"\" class=\"wp-image-1730\" width=\"840\" height=\"371\" srcset=\"https:\/\/i0.wp.com\/www.foxquestsystems.net\/foxblog\/wp-content\/uploads\/2020\/03\/T499-Changed-Logic-To-Existing-Activities-Screenshot.jpg?w=941&amp;ssl=1 941w, https:\/\/i0.wp.com\/www.foxquestsystems.net\/foxblog\/wp-content\/uploads\/2020\/03\/T499-Changed-Logic-To-Existing-Activities-Screenshot.jpg?resize=300%2C133&amp;ssl=1 300w, https:\/\/i0.wp.com\/www.foxquestsystems.net\/foxblog\/wp-content\/uploads\/2020\/03\/T499-Changed-Logic-To-Existing-Activities-Screenshot.jpg?resize=768%2C340&amp;ssl=1 768w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Viewing only logic changes to existing activities removes all other Logic changes that were created as a result of adding or deleting activities between the Control and Modified Projects. This approach focuses attention to logic changes that were intentionally made to existing activities.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00a9 2020 Copyright FoxQuest Systems, Inc. &#8211; All Rights Reserved<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Tracking logic changes can be a nightmare, especially when it comes to large CPM networks with ever changing scope and conditions. Many schedule specifications require that for each logic change, a description for the basis of each change is provided and specifically identifying the affected activities by Activity ID. In other words, the Owner is &hellip; <a href=\"https:\/\/www.foxquestsystems.net\/foxblog\/2020\/03\/14\/reporting-changed-logic-to-existing-activities\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Reporting Changed Logic to Existing Activities&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":1731,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","om_disable_all_campaigns":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[3],"tags":[],"class_list":["post-1729","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-comparison"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.foxquestsystems.net\/foxblog\/wp-content\/uploads\/2020\/03\/T498-Changed-Logic-To-Existing-Activities-Featured-Image.jpg?fit=821%2C452&ssl=1","_links":{"self":[{"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/posts\/1729","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/comments?post=1729"}],"version-history":[{"count":1,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/posts\/1729\/revisions"}],"predecessor-version":[{"id":1732,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/posts\/1729\/revisions\/1732"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/media\/1731"}],"wp:attachment":[{"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/media?parent=1729"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/categories?post=1729"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.foxquestsystems.net\/foxblog\/wp-json\/wp\/v2\/tags?post=1729"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}