<?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>Fixed/Float Latest vs Effective</title><link>https://www.aras.com/community/f/applications/3192/fixed-float-latest-vs-effective</link><description>Hello,

I am desiring in most applications to float to effective or released generations rather than latest generations. This results in released engineering BOM&amp;#39;s children components floating to the latest generation, which may be preliminary. I have</description><dc:language>ja-JP</dc:language><generator>Telligent Community 12</generator><item><title>RE: Fixed/Float Latest vs Effective</title><link>https://www.aras.com/community/thread/725?ContentTypeID=1</link><pubDate>Mon, 07 Aug 2017 05:32:48 GMT</pubDate><guid isPermaLink="false">916d3f7e-8ddc-42f8-8d45-380822f51406:42746f00-aa5d-43f8-be7f-7fd1fa58cc13</guid><dc:creator>Yoann Maingon</dc:creator><description>Hi,

The Released/effective/latest filter only apply on a part basis, not on a full bom. This is the role of the change manager to make sure that a BOM is not released with parts in preliminary states. We could also add some logic (method) during the release process to avoid that.

&amp;nbsp;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>