{"id":3611,"date":"2021-02-09T11:34:00","date_gmt":"2021-02-09T10:34:00","guid":{"rendered":"https:\/\/productip2.dev.peakfort.nl\/product-release\/requirement-fulfillments\/"},"modified":"2025-08-29T15:03:09","modified_gmt":"2025-08-29T13:03:09","slug":"requirement-fulfillments","status":"publish","type":"product-release","link":"https:\/\/www.productip.com\/de\/produkt-veroeffentlichung\/requirement-fulfillments\/","title":{"rendered":"Requirement fulfillments"},"content":{"rendered":"<p>For example the &#8218;Declaration of product identity&#8216; may not apply to your situation because your supplier always includes your article numbers in the documents he provides.<\/p>\n<p>Or a lot of your technical files may contain a requirement in a transition period, where both the old and new requirement are valid.<br \/>If you are ready to always use the new requirement, you can let the old requirement become &#8217;not applicable&#8216; automatically.<\/p>\n<p>Any requirement fulfillment you define, will be applied to new files you create.<br \/>And in existing files, if you change the market release date, region or product category, the requirement fulfillments are applied as well.<\/p>\n<p>The requirement fulfillments are only applied to requirements which have not been set to &#8217;not applicable&#8216; or &#8218;fulfilled&#8216; and have no notes and documents linked to them.<br \/>So if you manually add a note or document to a requirement or set it to &#8217;not applicable&#8216;, the automatic requirement fulfillments will never overrule what you did.<br \/>This allows you to manually make exceptions on a case-by-case basis after the&nbsp;automatic requirement fulfillments were initially applied.<\/p>\n<p>To use automatic requirement fulfillments, go to the &#8218;Requirement fulfillments&#8216; tab under &#8218;My account&#8216;.<\/p>\n<p>When adding a new&nbsp;requirement, you can choose between setting it to &#8218;Not applicable&#8216; with an optional note or &#8218;Fulfilled&#8216; with an optional note or document.<\/p>\n<p>By selecting &#8218;Apply to all versions&#8216;, the fulfillment applies to any version of the requirement, past, present and future.<\/p>\n<p>If you create a fulfillment for a requirement, it automatically applies to all its present and future amendments.<\/p>\n<p>If you want your requirement fulfillment to apply only in specific cases, you can restrict it to one or more file groups, risk levels or product categories.<br \/>Only if your technical file matches with one of them, the fulfillment is applied.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>For example the &#8218;Declaration of product identity&#8216; may not apply to your situation because your supplier always includes your article numbers in the documents he provides. Or a lot of your technical files may contain a requirement in a transition period, where both the old and new requirement are valid.If you are ready to always [&hellip;]<\/p>\n","protected":false},"featured_media":0,"template":"","class_list":["post-3611","product-release","type-product-release","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.productip.com\/de\/wp-json\/wp\/v2\/product-release\/3611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.productip.com\/de\/wp-json\/wp\/v2\/product-release"}],"about":[{"href":"https:\/\/www.productip.com\/de\/wp-json\/wp\/v2\/types\/product-release"}],"version-history":[{"count":1,"href":"https:\/\/www.productip.com\/de\/wp-json\/wp\/v2\/product-release\/3611\/revisions"}],"predecessor-version":[{"id":4558,"href":"https:\/\/www.productip.com\/de\/wp-json\/wp\/v2\/product-release\/3611\/revisions\/4558"}],"wp:attachment":[{"href":"https:\/\/www.productip.com\/de\/wp-json\/wp\/v2\/media?parent=3611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}