Loading

Agreements

Skip Feed
  1. Upcoming release in Snow Atlas - Agreements domain

     

    What’s happening: Modernizing SAM on Atlas – Agreements UI 

    What you’ll notice: Updated visual styling and improved consistency of Agreements pages in SAM on Snow Atlas, including introduction of functionalities and the deprecation of Agreement Search page. Expansion of Agreements' APIs to allow for more integrations and automations.

    What’s not changing: Core functionality, workflows, data, and existing integrations remain the same. 

    Why it matters: This change enables innovation, consistent reporting, and a more unified experience while enhancing agreements’ import and export functionalities. 

     

    What’s changing in Snow Atlas 

    We are modernizing SAM on Snow Atlas’ Agreements pages to improve visualizations and performance and introduce new APIs to improve automations and integrations. 

    With this release, we are introducing two relevant enhancements to the Agreements domain in Snow Atlas: 

    • Export enhancements: You will be able to export records directly from the Agreements list to CSV and XLSX file formats.  
    • Import improvements: You can now update agreements through import (previously, only creation of new agreements was possible). Note: This is limited to CSV files in the current release, with XLSX support in progress.  
    • Search page deprecation: The Agreements Search page will be deprecated. Use Agreements list filters for searching and Reports functionality for saving searches and scheduling exports. 

     

    Frequently Asked QuestionsDo I need to update integrations or APIs? 

    No changes are required for existing integrations. The new Agreements’ APIs are additive and will be documented on Snow Atlas documentation > API resources > SAM Core APIs > Agreements

     

    When will these changes happen? 

    The modernization of the SAM Agreements UI in Snow Atlas will be rolled out across several regions on May 6th and May 7th, 2026. Refer to the schedule below for specific maintenance windows: 

    Screenshot 2026-04-30 at 15.39.26During these windows, users in each region may experience temporary unavailability of the Agreements pages while updates are deployed. To minimize disruption, please:  

    • Ensure that any critical Agreements work is completed before the scheduled maintenance window.  
    • Consider scheduling exports or updates outside of these times to avoid interruptions.  
    • Communicate the maintenance schedule with your team to plan workflows accordingly. 

     

    Should I expect more changes to Agreements in the future? 

    Yes. Additional enhancements are planned, including:  

    • XLSX file support for agreement updates: Future updates will enable users to update agreements by importing XLSX files, in addition to CSV.  
    • Bulk editing of agreements: The ability to edit multiple agreements at once is coming, starting with standard fields, and later including custom fields.  
    • Improved filtering capabilities: Enhancements to the Agreements list’s filtering options are being evaluated and validated with customers and partners to make it easier to find and manage agreements. 

     

    Is there an opportunity to contribute with ideas and feedback? 

    Yes! The Flexera Product team welcomes community feedback. You can comment below, create an Idea on our IDEAS Board, or contact your account management representative to learn more about collaborating with the Product team. 

    Expand Post

    emonfre likes this.

    • You can't update multiple agreements at the same time via the Admin Menu Import Wizards, these only let you do imports and not updates.

       

      You will either have to do them manually one at a time or delete them from your agreements list and re-import them with the updated information.

       

      The latter is not a good option as any licenses etc. added to those agreements could also be deleted alongside any sub-agreement structure you have created.

      Expand Post

  2. Office Hours Q&A: Sorting Agreement Alerts by Expiration Date in Snow License Manager

    https://www.youtube.com/watch?v=gMNfQQY69S8&feature=youtu.be

     

    Question:

    Agreement Alerts - is there a way to sort by expiration date?

     

    Today the categories sort by critical, warning, etc. Within those categories I would like to be able to sort by most critical (10 days higher on the list than 30 days).

     

    Please view this video to hear @Chris Maher​ answer this question!

    Expand Post

  3. 1 of 2

  4. Autodesk licensing - current models (part 2 of 2)

     

    To continue the list from the blog post Autodesk licensing - current models (part 1 of 2)

     

    7. Personal Learning License.

    If the License Identification identifies the License Type as “Personal Learning”, then Licensee may Install a copy of the specific release of the Licensed Materials designated in the applicable License Identification on one (1) Computer, subject to certain functional limitations described in Section 6.3 (Affected Data), on a Stand-alone Basis, and permit Access to such copy of the Licensed Materials solely by Licensee, as an individual, solely for Personal Learning Purposes and only at and from locations that are not labs or classrooms and are not operated for commercial, professional or for-profit purposes. A Personal Learning License is for a fixed term specified in the applicable License Identification. If no such term is specified, the term is thirteen (13) months from Installation.

     

    8. Evaluation/Demonstration/Trial.

    If Autodesk identifies the License Type as a “demonstration”, “evaluation”, “trial,” “not for resale” or “NFR” version (each, an “Evaluation License”) in the applicable License Identification, Licensee may Install a copy of the specific release of the Licensed Materials designated in the applicable License Identification on one (1) Computer, subject to certain functional limitations described in Section 6.3 (Affected Data), on a Stand-alone Basis, and permit Access to such copy of the Licensed Materials, solely by Licensee’s Personnel, solely for Evaluation Purposes, only so long as the maximum number of concurrent Authorized Users does not exceed one (1), and only from Licensee’s work location. An Evaluation License is for a fixed term specified in the applicable License Identification, or if no such term is specified, the term is thirty (30) days from Installation or as otherwise authorized in writing by Autodesk.

     

    9. Fixed Term/Limited Duration/Rental License.

    If Autodesk identifies a license in the applicable License Identification as being for a specified period or limited duration or as having a fixed term or as a rental license, Licensee’s right to Install and Access the Licensed Materials will continue only for the period, duration or term specified in the License Identification. Such Installation and Access will be in accordance with and subject to the applicable License Type and Permitted Number. If Autodesk identifies a license in the applicable License Identification as being for a specified period or limited duration, or as having a fixed term, or a rental license but no period, duration or term is specified in the License Identification, the period, duration or term will be ninety (90) days from Installation (or the period specified in Sections B.6 (Educational Network License), B.7 (Personal Learning License) or B.8 (Evaluation/Demonstration/Trial) of this Exhibit B with respect to the licenses described in those sections).

     

    10. Session Specific Network License.

    If the License Identification identifies the License Type as a "Session Specific Network License", Licensee may install one (1) copy of the specific release of the Licensed Materials designated in the applicable License Identification on a Computer and permit Access to such Licensed Materials from multiple Computers through a Supported Virtualization Application, on a Networked Basis, solely by Licensee's Personnel, solely for Licensee's Internal Business needs, only so long as the maximum number of concurrent Sessions does not exceed the Permitted Number or other limits imposed by the Autodesk License Manager tool (if any). For purposes of this Session Specific Network License, (a) a “Session” is defined as a single interactive information exchange between two Computers that are connected through a Supported Virtualization Application, and (b) “Supported Virtualization Application(s)” are those third party virtualization applications or methods that are specifically identified as supported by Autodesk in the User Documentation for the Licensed Materials. With respect to the applicable Supported Virtualization Application, Licensee agrees to activate any available session tracking mechanism, not disable any such session tracking mechanism and to retain all records generated by such session tracking mechanism. A Session Specific Network License is for a perpetual term, except as other wise provided in this Agreement.

     

    Expand Post

  5. 1 of 2
    • Where I want to retain agreement information, but don't want it getting in the way, I rename the agreement by adding "ZZ REASON - " to the beginning. This means that my reports either filter out everything beginning ZZ, or only look at these. For the 'reason' I use things like RETIRED, CONSOLIDATED etc so that I know the reason why it is not in the main list. It's not elegant but it works (and when you list everything, all of the ZZ entries are at the bottom).
      Expand Post

  6. 1 of 3
    • Hi! I have a query for licenses which we are using daily: select ( case when i. type IS NOT then i. type   when i. type IS and c . AssignedID is not then 'Agreement'   when i. type IS and l. InvoiceReference is not or l. vendor IS NOT then 'Invoice'   else end ) AS 'Source'   , l. Vendor AS 'Vendor'   , IS( c . AssignedID, l. InvoiceReference) AS 'Invoice/agreement number'   , l. PurchaseDate AS 'Purchase date'   , m. Name AS 'Manufacturer'   , af . Name 'Product family'   , a . name AS 'LicensedProductName'   , l. ProductDescription AS 'ProductDescription'   , l. LegalLicenseCount AS 'Quantity'   , ( case when c . name like '%Open Value%' then 'Open Value'   when c . name like '%Open%' then 'Open'   when c . name like '%Enterprise Subscription 6%' then 'Enterprise Subscription 6'   when c . name like '%Get Genuine%' then 'Get Genuine'   When c . name like '%Select 6%' then 'Select 6'   when c . name like '%Enterprise 6%' then 'Enterprise 6'   when c . name like '%OSL 6%' then 'OSL 6'   when c . name like '%Enterprise 6%' then 'Enterprise 6'   when c . name like '%Enterprise Enrollment%' then 'Enterprise Enrollment'   when c . name like '%Select Enrollment%' then 'Select Enrollment' end ) AS 'License type/Program'   , ( case l. metric when '1' then 'Installations'   when '2' then 'Custom compare values'   when '7' then 'Number of processors'   when '8' then 'Number of processor cores'   when '9' then 'Users'   when '10' then 'Devices'   when '11' then 'Concurrent users'   when '12' then 'Concurrent devices'   when '13' then 'PVU'   when '14' then 'CAL (Client Access License)' end ) AS 'Metric'   , ( case when l. IsUpgrade = 1 then 'Upgrade' else 'Base' end ) AS 'Base/Upgrade license'   , cast( IS( l. IsSubscription, 0 ) as bit ) AS 'Subscription'   , l. SubscriptionValidTo AS 'Subscription end-date'   , cast( l. SA as bit ) AS 'Active SA'   , cast( ( case when l. IsSubscription = 1 and l. SubscriptionValidTo < getdate( ) then '0' else '1' end ) as bit ) AS 'Included in ELP'   from [ dbo] . [ tblLicense] l   left join [ dbo] . [ tblContract] c ON l. ContractID = c . ContractID   join [ dbo] . [ tblApplication] a ON a . ApplicationID = l. ApplicationID and l. cid = 1   join [ dbo] . [ tblApplicationFamily] af ON af . FamilyIndex = a . FamilyIndex   join [ dbo] . [ tblManufacturer] m ON m. ManufacturerID = a . ManufacturerID   left join [ dbo] . [ tblImport] i on i. ImportID = l. ImportID   order by [ LicensedProductName] ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ There is a mix of different sources used in this query (agreements, imports, etc.). Please, try this one and send feedback if you will want some additional data in. BR, Viktors
      Expand Post

  7. I haven't received email notification of agreement expiring

    I have set up a test email notification to notify me that an agreement is expiring by using a group criteria of the agreement name AND expires within the number of days left of the agreement but I haven't received an email notification. Is this because the email will be automatically sent at midnight of the day that the notification is set to be sent?

    Thank you


    1 of 3
    • Hi Paul, Thank you for you response - I am using version 8.3 and on Snow's product update list one of fixes for version 8.5 is 'FIX - E-mail notifications for agreements, for example, are now only sent out once when the notification criteria are met (PRB0041779).' so this might resolve the problem.  Are there any other settings I need to adjust for email notifications to work besides setting up the notification's details and criteria?

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
28 Posts
Loading
Agreements | Flexera