<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.aras.com/community/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Document Classification Changed to Change Controlled</title><link>https://www.aras.com/community/f/development/55315/document-classification-changed-to-change-controlled</link><description>We had to change an existing document classification from being not change controlled (ECN controlled) to now be change controlled (must be approved on an ECN.) 
 Now I need to update all of the documents that have this classification so they have the</description><dc:language>ja-JP</dc:language><generator>Telligent Community 12</generator><item><title>RE: Document Classification Changed to Change Controlled</title><link>https://www.aras.com/community/thread/10544?ContentTypeID=1</link><pubDate>Tue, 03 Sep 2024 07:35:04 GMT</pubDate><guid isPermaLink="false">916d3f7e-8ddc-42f8-8d45-380822f51406:1a712f6e-5c7b-4683-9638-22fbf929796b</guid><dc:creator>AngelaIp</dc:creator><description>&lt;p&gt;I haven&amp;acute;t completely understand your question. You want to use a different lifecycle map for existing items?&lt;/p&gt;
&lt;p&gt;I don&amp;acute;t understand right now why you cannot edit the classification property. Do you have classification specific lifecycles?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;You can reset the used lifecycle map by an admin action. But this will reset the complete lifecycle.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;(Translation is something like &amp;quot;set standard lifecycle&amp;quot;. Try it in a test database first).&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="/community/resized-image/__size/640x480/__key/communityserver-discussions-components-files/3/pastedimage1725348625497v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you already use different states for you items, you then have to re-promote the items after using the action. If you are open minded for a more dangerous but efficient approach: You can also use SQL to update the &amp;quot;state&amp;quot; and &amp;quot;current_state&amp;quot; property that are used for the LifeCycle. It maybe even eliminates the step to reset the lifecycle with the admin button, but I never tested this one. You basically need to know the id&amp;acute;s and names of the target states of your new lifecycles and directly modify them in the database. But try definitely in a test database first.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>