FlexNet Operations Knowledge Base

FlexNet Operations Cloud Reporter is an out-of-the-box solution for common reports using SAP BusinessObjects Business Intelligence (BI). Reporter is scheduled to upgrade from 4.2 to 4.3 in Production on May 12, 2024. Please be sure to review Reporter Upgrade FAQs available here. Information in this KB article is based on the new version and will be updated as more details become available. Key Information: FlexNet Operations Cloud ALM Reporter data is refreshed every 4 hours starting at UTC 00.00 FlexNet Operations Cloud LLM Reporter data is refreshed daily at approximately 5AM Pacific Time for data up to midnight. FlexNet Operations Cloud ALM Reporter database maintenance is scheduled every Sunday 2-6AM Pacific. Reporter users may observe slow performance or unresponsiveness during this time period. For this reason, we suggest scheduled reports to be outside this maintenance window. Key Resources: FAQs: Reporter Upgrade to 4.3 Reporter User Guide (ALM or LLM) FlexNet Operations Reporter 4.3 - Changes FlexNet Operations Reporter 4.3 - Known Issues Click the “Help” button in the main toolbar within Reporter for context sensitive help including links to more detailed guides from SAP. Check the Revenera Customer Community to access knowledge base articles or to enter a support case. This article is be updated as more information becomes available. Please subscribe to be notified of changes.

Introduction This article provides a running list of currently known issues with Reporter 4.3 which is scheduled to be available in the FlexNet Operations environment on the following dates: UAT: April 9, 2024 Production: May 12, 2024 (target date) Feature Use Cases Please review the list of known UAT Reporter 4.3 issues below. We will update this article as issues are resolved or added. Issue 1: Send From email errors When scheduling an emailed report from Reporter in UAT, populating the "Send From" field shows an error. Issue 2: Scheduled report history missing some scheduled instances [Resolved] When reviewing scheduled report history in UAT, most scheduled instances were migrated but some were not.   The few that were identified were resolved with an update to UAT Reporter. Issue 3: Missing Subscribed Alerts UAT Reporter is missing subscribed alerts for data refresh completion. Issue 4: Recent Documents not working [Resolved] The "Recent Documents" section in UAT does not seem to display recently reviewed documents.   Refreshing and saving document will address display in the "Recent Documents" section.   More Information For more information about the Reporter functionality, please see the Reporter User Guide (ALM or  LLM).

Introduction This article provides a running list of currently known changes present in Reporter 4.3. The new Reporter version is scheduled to be available in FlexNet Operations environments on the following dates: UAT: April 9, 2024 (available now) Production: May 12, 2024 (target date) Feature Use Cases Below is a list of Reporter changes we've identified in version 4.3, currently available in UAT.   The list is a summary and details can be found in the Reporter User Guide (ALM or  LLM) Time Zone  In version 4.2, the default time zone was Pacific Time. This has changed to UTC in version 4.3. You can change the time zone settings to ensure that scheduled objects are processed in the time zone you are working in.  See "Default Locale and Time Zone" in Reporter User Guide. The scheduled data refreshes have not changed. Object Organization  Object organization has changed significantly in version 4.3.  In version 4.2, personal folders were in the My Documents drawer; public folders were in the Folders drawer. In version 4.3, you access both folder types from the Folders tile.  See "Object Organization In Reporter" in the Reporter User Guide.   The interface for scheduling reports has changed significantly in version 4.3.   See "Scheduling Reports" in the Reporter User Guide. Date Format on Instance Time  Instances of scheduled reports are easily accessed on the Home tab in version 4.3.    To filter for these scheduled instances, you can add a date range under Instance Time with the dd/mm/yyyy format.  There is not an option today to change the format from dd/mm/yyyy to mm/dd/yyyy or other formats.   Export Option  In version 4.2, you could choose between export to Excel in .XLS and .XLSX format. In version 4.3, Excel documents are exported to .XLSX only.  Last Refresh Date Display In version 4.2, the document's last refresh date was displayed in the lower right corner on the results page.   In version 4.3, this default display is no longer an option but you can view the last refresh date in two ways: 1) You can view the last refresh date time of a document under Statistics in the Reading mode. 2) You can insert the Last Refreshed Date field as shown below when in the Design mode:     More Information For more information about the Reporter functionality, please see the Reporter User Guide (ALM  or LLM).  

Summary Display User Defined Fields in FNO Cloud (LLM) Reporter Synopsis User Defined Fields (UDFs) are additional customized fields which can be added to expand the FlexNet Operations service. They can be displayed to end users through your End-User Portal if included in your implementation or simply be used for reporting purposes. UDFs in FlexNet Operations Cloud LLM can be set at the following levels: Account, Member, Entitlement, Order Line, Catalog Item, Product and File. If you don't already have UDFs on your site and have questions or would like to implement some for reporting or application changes, please contact support for assistance. Discussion Since User Defined Fields are by their nature custom, they are shown in Reporter by an assigned UDF number (UDF 1 Value, UDF 2 Value, etc.) and not the name viewable in FlexNet Operations. To identify which UDF number matches to what you see in the application, you can run the standard report "UDF User Defined Field List": Below is an example of results from running the UDF User Defined Field List showing the mapping of each UDF number by level. In this example, Account Level UDF 1 represents Image URL, Account Level UDF 2 represents Corporate Account Identifier, etc. Note that the data below is based on a demo site so not indicative of your implementation. Once you know which UDF number maps to the UDFs want to add to your report, you can select the appropriate UDF number value. Below example shows where the Account User Defined Field folder and UDF label and value: If you didn't run the report to identify which value to use or just want to be sure you mapped correctly, you can also include both the label and the value for each UDF (note it will only show the label if there is a value to report): You can then change the column header to be more descriptive than the object name. Double click on the column header and set to the name of the UDF (Example, replace Account UDF Value 1 with Image URL and Account UDF Value 2 with Corporate Account Identifier). Remove the label fields if desired:

We've prepared this article to help you navigate the Reporter upgrade to 4.3. Why is Reporter being upgraded? The Reporter upgrade is required to maintain compatibility with the updated hosting infrastructure for FlexNet Operations.  Will there be changes to the functionality? Reporter 4.3 features several user interface and navigation changes. There is no change to the supported Reporter functionality as it relates to FlexNet Operations. For a list of changes affecting core functionality, please see the FlexNet Operations Reporter 4.3 - Overview  knowledge article. We will publish the updated FlexNet Operations Reporter User Guide on docs.revenera.com when it is complete. How does the upgrade affect existing scheduled reports? There is no expected impact to data, existing reports, or their scheduled instances. Anything in place will be carried over from the previous version and will run as expected. Any reports created, scheduled, or modified during the following blackout period will not be reflected in the new Reporter version. UAT (April 1, 2024 - April 9, 2024) and Production (May 1, 2024 - May 12, 2024). What steps (if any) do users need to take? After the Reporter upgrade in UAT on April 9, 2024, we strongly recommend users familiarize themselves with the new Reporter user interface and verify their reports. If any issues are observed, please contact Revenera Technical Support immediately to allow time to diagnose and resolve the issue before the planned Production upgrade on May 12, 2024. What resources are available to learn the new Reporter? To assist with enablement, please refer to the the FlexNet Operations Reporter 4.3 - Overview  knowledge article. We will provide the updated FlexNet Operations Reporter User Guide when it is complete. Who can I contact if I need assistance with the new Reporter? If you have any questions or encounter any issues with the new Reporter, please reach out to the Revenera Technical Support for assistance.

Summary After installing the 2023 R1 and upgrading the FNO, CLS, and UAS databases from an older FNO version, attempting to preview available features for a device from an FNE.NET KIT results in a "Back Office Server Error". The error code is [1,7E6,9,0[7000001C,7100002E,250137]]. Symptoms When trying to use the FNE .NET Toolkit for Capability Request Previews the error below screenshot is thrown. The error describes an issue with an un-supported datatype on the table gls_feature. The DB used here is AWS RDS SQL Server Standard Edition. Steps to Reproduce 1. Prepare the Environment: Import a customer database that has not been upgraded to the latest version. 2. Upgrade CLS Database: Access the FNO setup page:  "http://localhost:4321/flexnetsetup" Use the "Manage Schema" option for the CLS database. 3. Deploy and Start Services: Deploy the FNO, UAS, and LFS services. Start the FNO service, ensuring it points to the recently upgraded customer database (not the original, non-upgraded one). 4. Trigger the Error: Use the .NET FNE KIT to send a "Preview Capability Request".  Expected Result: The .NET FNE KIT should show the available features Results we are getting: The .NET FNE KIT is throwing an error.   Workaround The FNO upgrade scripts fail to upgrade the data types of a few columns on the table "gls_feature". TEXT datatype of a column is deprecated in the SQL server and some of the versions of SQL server don't support having distinct TEXT fields. Changing the columns with TEXT datatype to Varchar(Max) is recommended.  The below steps are performed on the DB. Check if ALLOW_SNAPSHOT_ISOLATION is on for clsdb or not The below query can be used to check the same :  SELECT snapshot_isolation_state_desc from sys.databases where name='clsdb'; If not enabled use the below query to enable the same : ALTER DATABASE clsdb SET ALLOW_SNAPSHOT_ISOLATION ON; In this case, the ALLOW_SNAPSHOT_ISOLATION was off for this DB and we had to enable to make changes to the table structure of dbo.gls_feature Change datatypes for a few columns on table dbo.gls_feature Kindly execute the below queries : ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN vendor varchar(MAX); ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN issuer varchar(MAX); ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN issued datetime; ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN notice varchar(MAX); ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN serialnumber varchar(MAX);   ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN starts datetime; ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN expiry datetime; Fix Version and Resolution The BUG will be fixed in future releases. 

This article lists the current year's past releases for FlexNet Operations Cloud. For upcoming releases, please see the Software Monetization Release Schedule. (NOTE: This requires you to log into the community as a Revenera customer. ) 2024 Releases -  FlexNet Operations Cloud ALM Release ALM Deployment Environment Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2024.02 Legacy AWS NAM/EU   January 30, 2024 Deferred     AWS NAM/EU   January 31, 2023 February 15, 2024   2024.01 Legacy AWS NAM/EU   January 3, 2024 January 16, 2024     AWS NAM/EU   January 4, 2024 January 17, 2024     FlexNet Operations Cloud LLM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2024.02   January 30, 2024 February 15, 2024   2024.01   January 3, 2024 January 16, 2024     2023 Releases -  FlexNet Operations Cloud ALM Release ALM Deployment Environment Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2023.09 Data Center Legacy AWS NAM AWS EU   Wednesday, Aug 30, 2023 Tuesday, Sep 12, 2023     AWS Migrated (CLS & UAS)   Thursday, Aug 31, 2023 Wednesday, Sep 13, 2023   2023.08 Data Center Legacy AWS NAM AWS EU   Wednesday, Jul 26, 2023 Wednesday, Aug 9, 2023     AWS Migrated (CLS & UAS)   Thursday, Jul 27, 2023 Thursday, Aug 10, 2023   2023.07 Data Center Legacy AWS NAM AWS EU Monday, Jun 12, 2023 Tuesday, Jun 27, 2023 Tuesday, Jul 11, 2023     AWS Migrated (CLS & UAS)   Wednesday, Jun 28, 2023 Wednesday, Jul 12, 2023   2023.06     Thursday, May 25, 2023 Thursday, Jun 8, 2023   2023.06 (CLS)     Friday, Jun 2, 2023 Friday, Jun 9, 2023   2023.05     Saturday, Apr 29, 2023 Tuesday, May 9, 2023   2023.04     Thursday, Mar 16, 2023 Monday, Apr 3, 2023   2023.03     Wednesday, Feb 22, 2023 Wednesday, Mar 8, 2023   2023.03 (CLS)     Thursday, Feb 23, 2023 Data Center | AWS EMEA | AWS NAM: Wednesday, Mar 8, 2023 AWS Migrated: Thursday, Mar 9, 2023   2023.02     Monday, Jan 30, 2023 Monday, Feb 13, 2023   2023.02 (CLS)     Tuesday, Jan 31, 2023 Monday, Feb 13, 2023   2023.01   Tuesday, Jan 17, 2023 Data Center: Wednesday, Jan 4, 2023 AWS EMEA/NAM: Thursday, Jan 5, 2023 Data Center: Wednesday, Jan 18, 2023 AWS EMEA/NAM: Thursday, Jan 19, 2023   2023.01 (CLS)     Thursday, Jan 5, 2023 Data Center: Thursday, Jan 19, 2023 AWS EMEA/NAM: Friday, Jan 20, 2023     FlexNet Operations Cloud LLM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2023.09   Wednesday, Aug 30, 2023 Tuesday, Sep 12, 2023   2023.09 (CLS & UAS)   Thursday, Aug 21, 2023 Wednesday, Sep 13, 2023   2023.08   Wednesday, Jul 26, 2023 Wednesday, Aug 9, 2023   2023.08 (CLS & UAS)   Thursday, Jul 27, 2023 Thursday, Aug 10, 2023   2023.07   Tuesday, Jun 27, 2023 Tuesday, Jul 11, 2023   2023.07 (CLS & UAS)   Wednesday, Jun 28, 2023 Wednesday, Jul 12, 2023   2023.06 Wednesday, May 24, 2023 Thursday, May 25, 2023 Thursday, Jun 8, 2023   2023.06 (CLS)   Friday, Jun 2, 2023   Friday, Jun 9, 2023   2023.05   Tuesday, Apr 25, 2023 Tuesday, May 9, 2023   2023.04   Thursday, Mar 16, 2023 Monday, Apr 3, 2023   2023.03   Wednesday, Feb 22, 2023 Wednesday, Mar 8, 2023   2023.03 (CLS)   Thursday, Feb 23, 2023 Data Center | AWS EMEA | AWS NAM: Wednesday, Mar 8, 2023 AWS Migrated: Thursday, Mar 9, 2023   2023.02   Monday, Jan 30, 2023 Monday, Feb 13, 2023   2023.02 (CLS)   Tuesday, Jan 31, 2023 Monday, Feb 13, 2023   2023.01 Tuesday, Jan 17, 2023 Wednesday, Jan 4, 2023 Wednesday, Jan 18, 2023   2023.01 (CLS)   Thursday, Jan 5 2023 Thursday, Jan 19, 2023    *May include system changes only and no release changes. Please see FlexNet Operations News for confirmation.   2022 Releases -  FlexNet Operations Cloud ALM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2022.12 Wednesday, Nov 30, 2022 Thursday, Dec 1, 2022 Thursday, Dec 15, 2022   2022.12 (CLS)   Friday, Dec 2, 2022 Thursday, Dec 15, 2022   2022.11   Wednesday, Nov 2, 2022 Thursday, Nov 17, 2022   2022.10 Monday, Nov 7, 2022 Thursday, Sep 29, 2022 Thursday, Oct 13, 2022   2022.09   Tuesday, Aug 30, 2022 Tuesday, Sep 13, 2022   2022.08   Thursday, Jul 28, 2022 Thursday, Aug 11, 2022   2022.07   Tuesday, Jun 28, 2022 Tuesday, Jul 12, 2022   2022.07 (CLS only)   Tuesday, Jun 28, 2022 Monday, Jul 4, 2022   2022.06   Thursday, May 26, 2022 Thursday, Jun 9, 2022   2022.05 Monday, May 2, 2022 Wednesday, May 4, 2022 No production release   2022.04   Thursday, Mar 31, 2022 Thursday, Apr 14, 2022   2022.03 (CLS)   Friday, Feb 18, 2022 Thursday, Feb 24, 2022 No 2022.03   Wednesday, Mar 2, 2022 Tuesday, Mar 15, 2022 No 2022.02 Tuesday, Jan 25, 2022 Thursday, Jan 27, 2022 Saturday, Feb 12, 2022 Yes 2022.01   Tuesday, Dec 21, 2021 Tuesday, Jan 11, 2022 No   FlexNet Operations Cloud LLM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2022.12 Wednesday, Nov 30, 2022 Thursday, Dec 1, 2022 Thursday, Dec 15, 2022   2022.12 (CLS)   Friday, Dec 2, 2022 Thursday, Dec 15, 2022   2022.11   Wednesday, Nov 2, 2022 Thursday, Nov 17, 2022   2022.10 Monday, Nov 7, 2022 Thursday, Sep 29, 2022 Thursday, Oct 13, 2022   2022.09   Tuesday, Aug 30, 2022 Tuesday, Sep 13, 2022   2022.08   Thursday, Jul 28, 2022 Thursday, Aug 11, 2022   2022.07   Tuesday, Jun 28, 2022 Tuesday, Jul 12, 2022   2022.06   Thursday, May 26, 2022 Thursday, Jun 9, 2022   2022.05 Monday, May 2, 2022 Wednesday, May 4, 2022 No production release   2022.04   Thursday, Mar 31, 2022 Thursday, Apr 14, 2022   2022.03 (CLS)   Friday, Feb 18, 2022 Thursday, Feb 24, 2022 No 2022.03   Wednesday, Mar 2, 2022 Tuesday, Mar 15, 2022 No 2022.02 Tuesday, Jan 25, 2022 Thursday, Jan 27, 2022 Saturday, Feb 12, 2022 Yes 2022.01   Tuesday, Dec 21, 2021 Tuesday, Jan 11, 2022 No *May include system changes only and no release changes. Please see FlexNet Operations News for confirmation.   2021 Releases -  FlexNet Operations Cloud ALM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2021.12   Friday, Dec 3, 2021 Thursday, Dec 16, 2021 No 2021.12 (CLS)   Friday, Dec 3, 2021 Thursday, Dec 9, 2021 No 2021.11 Monday, Nov 1, 2021 Tuesday, Nov 2, 2021 Tuesday, Nov 16, 2021 No 2021.11 (CLS)   Thursday, Nov 4, 2021 Tuesday, Nov 16, 2021 No 2021.10   Thursday, Sep 30, 2021 Wednesday, Oct 13, 2021 No 2021.10 (CLS)   Thursday, Oct 7, 2021 Saturday, Oct 23, 2021 Yes 2021.09 Monday, Aug 30, 2021 Tuesday, Aug 31, 2021 Tuesday, Sep 14, 2021 No 2021.08   Thursday, Jul 29, 2021 Thursday, Aug 12, 2021 No 2021.07   Tuesday, Jun 29, 2021 Thursday, Jul 15, 2021 No 2021.06   Thursday, Jun 3, 2021 Thursday, Jun 17, 2021 No 2021.06 (CLS)   Friday, Jun 11, 2021 Tuesday, Jun 22, 2021 No 2021.05 Tuesday, Apr 20, 2021 - Wednesday, Apr 21, 2021 Thursday, Apr 22, 2021 Saturday, May 15, 2021 Yes 2021.05 (CLS)   Thursday, Apr 22, 2021 Tuesday, May 11, 2021 No 2021.04   Wednesday, Apr 7, 2021 Tuesday, Apr 13, 2021 No 2021.03   Tuesday, Mar 2, 2021 Tuesday, Mar 16, 2021 No 2021.02 Wednesday, Jan 27, 2021 Thursday, Jan 28, 2021 Thursday, Feb 11, 2021 No 2021.01   Thursday, Dec 17, 2020 Tuesday, Jan 12, 2021 No 2021.01 (CLS)   Thursday, Dec 17, 2020 Saturday, Jan 16, 2021 Yes   FlexNet Operations Cloud LLM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2021.12   Friday, Dec 3, 2021 Thursday, Dec 16, 2021 No 2021.12 (CLS)   Friday, Dec 3, 2021 Thursday, Dec 9, 2021 No 2021.11 Monday, Nov 1, 2021 Tuesday, Nov 2, 2021 Tuesday, Nov 16, 2021 No 2021.11 (CLS)   Thursday, Nov 4, 2021 Tuesday, Nov 16, 2021 No 2021.10   Thursday, Sep 30, 2021 Wednesday, Oct 13, 2021 No 2021.10 (CLS)   Thursday, Oct 7, 2021 Saturday, Oct 23, 2021 Yes 2021.09* Monday, Aug 30, 2021 Tuesday, Aug 31, 2021 Tuesday, Sep 14, 2021 No 2021.08   Thursday, Jul 29, 2021 Thursday, Aug 12, 2021 No 2021.07 (CLS only)   Tuesday, Jun 29, 2021 Thursday, Jul 15, 2021 No 2021.06   Thursday, Jun 3, 2021 Thursday, Jun 17, 2021 No 2021.06 (CLS)   Friday, Jun 11, 2021 Tuesday, Jun 22, 2021 No 2021.05 Tuesday, Apr 20, 2021 - Wednesday, Apr 21, 2021 Thursday, Apr 22, 2021 Saturday, May 15, 2021 Yes 2021.05 (CLS)   Thursday, Apr 22, 2021 Tuesday, May 11, 2021 No 2021.04   Wednesday, Apr 7, 2021 Tuesday, Apr 13, 2021 No 2021.03   Tuesday, Mar 2, 2021 Tuesday, Mar 16, 2021 No 2021.02 Wednesday, Jan 27, 2021 Thursday, Jan 28, 2021 Thursday, Feb 11, 2021 No 2021.01   Thursday, Dec 17, 2020 Tuesday, Jan 12, 2021 No 2021.01 (CLS)   Thursday, Dec 17, 2020 Saturday, Jan 16, 2021 Yes *May include system changes only and no release changes. Please see FlexNet Operations News for confirmation. 2020 Releases -  FlexNet Operations Cloud ALM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2020 R1 Wednesday, Jan 8, 2020 Thursday, Jan 9, 2020 Thursday, Feb 6, 2020 No 2020 R1 SP1   Monday, Feb 24, 2020 Monday, Mar 09, 2020 No 2020 R1 SP2   Thursday, Mar 26, 2020 Thursday, Apr 09, 2020 No 2020 R2 Wednesday, Apr 13, 2020 Tuesday, Apr 14, 2020 Wednesday, May 20, 2020 No 2020 R2 SP1   Thursday, Jun 4, 2020 Thursday, Jul 2, 2020 No 2020 R3 Friday, Jul 10, 2020 PCS: Wednesday, Jul 15, 2020 UAT: Monday, Jul 27, 2020 Thursday, Aug 13, 2020 No 2020 R3 (CLS)     Saturday, Aug 15, 2020 Yes 2020 R3 SP1   Thursday, Sep 3, 2020 Tuesday, Sep 22, 2020 No 2020 R3 SP1 Hotfix (CLS)   Thursday, Sep 17, 2020 Thursday, Oct 1, 2020 No 2020 R3 SP2   Wednesday, Sep 30, 2020 Wednesday, Oct 14, 2020 No 2020 R3 SP2 (CLS)   Wednesday, Sep 30, 2020 Wednesday, Nov 4, 2020 No 2020 R3 SP3 Friday, Oct 30, 2020 - Monday, Nov 2, 2020 Tuesday, Nov 3, 2020 Thursday, Dec 3, 2020 No 2020 R3 SP3 (CLS only)   Monday, Nov 23, 2020 Thursday, Dec 3, 2020 No   FlexNet Operations Cloud LLM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2020 R1 Wednesday, Jan 8, 2020 Thursday, Jan 9, 2020 Thursday, Feb 6, 2020 No 2020 R1 SP1   Monday, Feb 24, 2020 Monday, Mar 09, 2020 No 2020 R1 SP2   Thursday, Mar 26, 2020 Thursday, Apr 09, 2020 No 2020 R2 Wednesday, Apr 13, 2020 Tuesday, Apr 14, 2020 Wednesday, May 20, 2020 No 2020 R2 SP1   Thursday, Jun 4, 2020 Thursday, Jun 18, 2020 No 2020 R3 Friday, Jul 10, 2020 PCS: Wednesday, Jul 15, 2020 UAT: Monday, Jul 27, 2020 Thursday, Aug 13, 2020 No 2020 R3 (CLS)     Saturday, Aug 15, 2020 Yes 2020 R3 SP1   Thursday, Sep 3, 2020 Tuesday, Sep 22, 2020 No 2020 R3 SP1 Hotfix (CLS)   Thursday, Sep 17, 2020 Thursday, Oct 1, 2020 No 2020 R3 SP2   Wednesday, Sep 30, 2020 Wednesday, Oct 14, 2020 No 2020 R3 SP2 (CLS)   Wednesday, Sep 30, 2020 Wednesday, Nov 4, 2020 No 2020 R3 SP3 Friday, Oct 30, 2020 - Monday, Nov 2, 2020 Tuesday, Nov 3, 2020 Thursday, Dec 3, 2020 No 2020 R3 SP3 (CLS only)   Monday, Nov 23, 2020 Thursday, Dec 3, 2020 No  

Points to remember: 1. Under the System > System Configuration > End-User Portal Setup > Select 'Entitlements Page' > 'Hide Split' option must be unchecked. 2. Ensure that 'Split Line Items or Bulk Entitlements' permission is selected for the user's role who is performing the split operation. 3. The split operation can be performed on the end user portal, when the entitlement is linked to the distributor(Channel Partner Account) without the information of end customer account[UNKNOWN_ORG_UNIT (Information Not Available)]. 4. One of the partner tiers (either the partner account or one of its sub-accounts) of an entitlement must be set as Current Owner before an entitlement can be split. 5. A new related customer account can be created while performing the split entitlement. To assign entitlement for newly created Related Customer Account: Click on 'Search Account' icon that is present next to the 'Target Account' > Hover over the Action menu > The option to create a new related customer account is available and the account can be created > After creating this account, select this account to split. 6. For the Distribution Type/Tier Name: Distributor, A new related partner account cannot be created and this action will fail with the error message "Cannot split to tier Distributor; this tier has already been defined on the entitlement."   Instructions: Step 1: Click on create option under the Entitlements menu in the Producer portal.  Step 2: Link the entitlement to any Channel Partner account(Distributor) and click on 'Save'. Step 3: Add a new line item for the entitlement and then click on 'Save & Deploy' button. Step 4: Log in to the end user portal with user credentials. Step 5: Under 'Activations & Entitlements' menu, click on 'List Entitlements' and search for the Entitlement-id/Activation-id that require splitting. Step 6: Select the check box, hover over the 'Action' button and click on 'Split' option. Step 7: Enter the value for 'Split Amount'. Click on search icon, select the 'Target Account' value and 'Save' it.(Note: User can add the new customer account and assign split amount)  Step 8: Next, click the 'Split' button before clicking 'Ok'.  Step 9: The selected line item will be split.   

FlexNet Operations Cloud Reporter is an out-of-the-box solution for common reports using SAP BusinessObjects Business Intelligence (BI).   The newest version of Reporter (4.2) is available alongside the older version until the older version is deprecated on August 6, 2021.  Please be sure to review Reporter Upgrade FAQs available here. Information in this KB article is based on the new version. Key Information: FlexNet Operations Cloud ALM Reporter data is refreshed every 4 hours starting at UTC 00.00.  FlexNet Operations Cloud LLM Reporter data is refreshed daily at approximately 5AM Pacific for data up to midnight. FlexNet Operations Cloud ALM Reporter database maintenance is scheduled every Sunday 2-6AM Pacific. Reporter users may observe slow performance or unresponsiveness during this time period. For this reason, we suggest scheduled reports to be outside this maintenance window.  Key Resources: Reporter Upgrade FAQs Reporter: Transition Readiness Guide Reporter User Guide - Online / PDF How to Access Reporter How to Create and Save a Document How to Edit an Existing Document How to Send and Share a Document (pending) * How to Run a Standard Report - ALM / LLM SAP Tutorials Click the “Help” button in the main toolbar within Reporter for context sensitive help including links to more detailed guides from SAP. Check the Revenera Customer Community to access the Reporter User Guide, knowledge base articles or to enter a support case. * For more detail on current or pending articles, please see the Reporter User Guide.  

Summary Start/Stop of FlexNet Operation(FNO) is not working using FlexNet setup  when FNO is installed in Service mode In Linux systems. This  BUG is applicable only to Linux build of FNO and on any version later than 2018R1 SP1 until 2023R1. Symptoms Up on the installation of FNO and after doing configuration using FlexNet Setup (i.e http://localhost:4321/flexnetsetup), when the user tries to click the "Start Server"  button present under "System Status",  the server doesn't start. Steps to Reproduce Install the FlexNet Operation on any Linux system using Linux build. Launch FlexNet Setup i.e http://localhost:4321/flexnetsetup Make the configuration present under General and Database tab and make sure to select "Install as  a Service" in General tab. Click "Start Server" from  System status in order to start the server Workaround Following are few workarounds for the BUG, which can be followed: Uncheck the config "install as a service"  and  then use  FlexNet Setup to start/stop the FNO services. (OR) Start the services using standalone.sh located in <FNO_HOME>/components/wildfly/bin folder. Fix Version and Resolution BUG will be fixed in future releases  and most likely in 2024R1 onwards.

Introduction Steps to be followed to unmap non-metered licenses from CLS. Instructions 1) Enable the Admin user: Goto end user portal -> license server -> give CLS ID-> set password. This is the admin password.     2) In REST API using POSTMAN: i) POST https://flex<tenantid>.compliance.flexnetoperations.com/api/1.0/instances/<CLS_ID>/authorize   Body -> RAW {     "user": "admin",     "password": "<password>" }     ii) Bearer Token -> Got from Step 1,can be used to get the features and clients of the CLS:   GET https://flex<tenant_ID>.compliance.flexnetoperations.com/api/1.0/instances/<CLS_ID>/features GET https://flex<tenant_ID>.compliance.flexnetoperations.com/api/1.0/instances/<CLS_ID>/clients   iii) Delete operation once you get the client ID for the CLS from the above request(/clients):   DELETE https://flex<tenant_ID>.compliance.flexnetoperations.com/api/1.0/instances/<CLS_ID>/clients/<client_id> More Information Post these steps, you should be able to see the counts to be mapped to any CLS.

Introduction This article provides the FlexNet Operations Cloud IP addresses for network block or IP address allow list. Need to Know A new set of network blocks is being used by FlexNet Operations Cloud services. The networks block addresses differ based on the deployment environment your FlexNet Operations Cloud is hosted on. We are migrating from the following legacy IP blocks referred in the table below. Please add the new IP blocks documented in the Best Practices section based on your FlexNet Operations instance and its deployment region. Legacy IP address blocks (for reference) Environment IPv4 Blocks IPv6 Blocks Production 64.14.29.0/24 2620:122:f001:1163::/64 UAT 64.14.29.0/24 2620:122:f001:1163::/64 Disaster Recovery (DR) 64.27.162.0/24 2620:122:f001:1163::1/128 Best Practices If you use an IP allow list, we advise using IP blocks instead of individual IP addresses as the IP addresses for a given connection may change from one call to the next. We strongly recommend sharing the following IP blocks with your IT team to add to your network block. For FlexNet Operations Cloud ALM instances: IPv4: AWS NAM: 185.146.155.0/24 IPv6: AWS NAM: 2620:122:f003::/48 -OR- Deployment Region Environment IPv4 Blocks IPv6 Blocks AWS NAM Production 185.146.155.64/27 2620:122:f005::/56 UAT 185.146.155.0/27 2620:122:f003::/56 Production Copy Service (PCS) 185.146.155.32/27 2620:122:f004::/56 AWS EU Production 185.146.152.64/27 2a07:4f80:20:200::/56 UAT 185.146.152.0/27 2a07:4f80:20::/56 NOTE: It is no longer necessary to specify an IP address block for the Disaster Recovery (DR) environment. For FlexNet Operations Cloud LLM instances: We are in the process of migrating FlexNet Operations LLM to AWS. We advise adding the following IP blocks to your network block to prepare for the upcoming migration. IPv4: AWS NAM: 185.146.155.0/24 IPv6: AWS NAM: 2620:122:f003::/48 -OR- Deployment Region Environment IPv4 Blocks IPv6 Blocks AWS NAM Production 185.146.155.64/27 2620:122:f005::/56 UAT 185.146.155.0/27 2620:122:f003::/56 Production Copy Service (PCS) 185.146.155.32/27 2620:122:f004::/56 NOTE: It is no longer necessary to specify an IP address block for the Disaster Recovery (DR) environment. Frequently Asked Questions Understanding IP Allow Listing for FlexNet Operations Cloud Q: Why do we need to allow list these blocks? A: If your organization, or your customers, operate strict firewall rules then you should allow these IP address blocks. Q: Who should we speak to about allow listing? A: You should discuss your needs with your IT administrators, who typically maintain these allow list rules. If you require further information, please contact Revenera Technical Support. Q: Which FlexNet Operations Cloud services are affected if an allow list is configured? A: All services can be impacted if you are using an allow list. Examples include: Your employees connecting to the Producer Portal UI Your end customers connecting to the Customer Portal UI Your CRM system calls FNO Web Services Your end customers' devices or Local License Servers making call-home or synchronization connections to FNO Your end customers' devices connecting to Cloud License Servers to make Capability Requests Q: Why do we need to configure an entire block – can't we just allow the IP address associated with the end point we use? A: Our advice has always been to configure the block. When we move to AWS, this is even more important, because AWS does not allocate static IP addresses; the IP address allocated to a URL can change dynamically. Understanding the AWS Migration's Affect on FlexNet Operations Cloud Allow Listing Q: When will these changes take place? A: The IP addresses were assigned on 2022-11-23 and as FlexNet Operations services were migrated over to the new AWS environment, we reminded customers to add these IP blocks to their network block to ensure continued access to FlexNet Operations services. Q: Why can't you continue to use the old IP address blocks indefinitely instead of using the new IP address blocks? A: Using the legacy IP address blocks involves complex routing rules which will impact performance, and so we must move to the new blocks  as part of the AWS migration. Q: What will happen if the addresses are not added to the allow list? A: If you or your customers impose strict firewalls rules, FlexNet Operations and its services may not be accessible.

Introduction The SSL (Secure Sockets Layer) certificate for FlexNet Operations Cloud is updated annually. Periodically the intermediate (about every 10 years) and root (about every 20 years) certificates are also updated. The FlexNet Embedded local license server relies on the intermediate and root certificate chain to communicate with FlexNet Operations Cloud.  The following instructions are best practices to have a local license server prepared for this and other future certificate updates in FlexNet Operations Cloud. Who Should Read This Article? The intended audience for this article includes FlexNet Embedded local license server administrators, who need to ensure that their license servers are properly configured for an SSL certificate update. (The "you" in this article is the local license server administrator.) Producers should also read this article to understand what the local license server administrator at each of their customer sites must do to prepare for an upcoming certificate update. Producers need to keep the license server administrators informed of announcements about upcoming certificate updates and expirations. With support from producers, license server administrators can have adequate time to prepare their license servers for certificate upgrades and test a new certificate in UAT before the old certificate actually expires. Local License Servers 2021.05 or Later In general, a certificate update is not a concern for FlexNet Embedded local license servers built with the 2021.05 or newer FlexNet Embedded kits as these servers default to using the “cacerts” file included with Java. The “cacerts” file is maintained and updated by Java. Certificate authorities start issuing new intermediate and root certificates 1-2 years before their actual expiration date. This allows time for the “cacerts” file to be updated well before the change occurs with certificates for FlexNet Operations Cloud. Keeping Java updated to the latest version supported by your local license server helps to ensure that the server's certificate information will be properly synchronized with the FlexNet Operations Cloud certificates whenever certificate updates go into effect. (Refer to the FlexNet Embedded License Server Release Notes for the latest versions of Java supported by the license server.) Local License Servers 2021.03 or Earlier If you are using a local license server built with FlexNet Embedded 2021.03 or earlier, check the truststore path in the server’s “local-configuration.yaml” file.  (On Linux, this file is found in the “/opt/flexnetls/producer” directory. On Windows, it is located in the same directory as “flexnetls.jar”.) If this file is configured to use the “cacerts” file as its truststore, no action is needed.  If the file is configured to use the “flexnet.certs” file, the license server administrator can perform one of these two options. Whichever option is used, the license server administrator should make sure that the Java version is kept up to date with the latest version supported by the local license server. (See the FlexNet Embedded License Server Release Notes for this information.)  Option 1 First, update the “local-configuration.yaml” so that it contains the path to the Java “cacerts” file, as shown in the following example: # Path to truststore containing server certificate. truststore-path: ${JAVA_HOME}/jre/lib/security/cacerts Then, for the “truststore-password” property, enter the password for the “cacerts” truststore. Note that, if the password was not previously changed from its default value, enter the default password “changeit”. However, if the password was previously changed, the current password must be entered. # Truststore password. You can obfuscate this with java -jar flexnetls.jar -password  your-password-here. truststore-password: changeit Alternatively, the administrator can first obfuscate the password by following the instructions included in the “yaml” file and then provide the obfuscated value, as shown is this example. truststore-password: OBF:1vn21ugu1saj1v9i1v941sar1ugw1vo0 Option 2 Install a version of the local license server built with FlexNet Embedded 2021.05 or later. Local Licenses Servers That Run Offline Except for Activations Some FlexNet Embedded local license servers run offline but occasionally go online to activate the latest licenses from the FlexNet Operations back office. To ensure that the certificate information on the license server is synchronized with FlexNet Operations before performing any activations, the license server administrator needs to do the following: Bring the offline device (containing the license server) online. Ensure that the device is upgraded with the latest version of Java supported by your license server installation. (See the FlexNet Embedded License Server Release Notes.) Ensure that the “local-configuration.yaml” file for the license server points to the “cacerts” file as its truststore. This step is especially important if your license server version is 2021.03 or earlier. For more information, see Local License Servers 2021.03 or Earlier. Perform the license activation operations. This step is important (as explained in The SSL Communication Process). Take the device offline. The SSL Communication Process During SSL communication between the server (FlexNet Operations) and a client (the local license server), an initial "handshake" occurs. During this handshake, the root certificate present in caecerts gives the client a public key to attempt validation. Once validation is successful, the connection is established and further communication can occur. For offline local license servers, bringing the license server temporarily online to perform activation operations once you have prepared it for a certificate upgrade is necessary to ensure that the initial SSL handshake using the new certificate takes place. Troubleshooting If your local license server has not been properly configured for a certificate upgrade, the license server receives the message "SSL is misconfigured" once the old certificate expires. At this point, to avoid any further license-server downtime, you must perform the steps outlined in this article to ensure that the license server is able to use the new certificate. However, because of this late configuration, you will have missed the UAT phase of the upgrade that allowed you to test the new certificate and resolve any issues before the old certificate expired.  Once you have configured your machine for a certificate upgrade, it should be able to handle future certificate upgrades (as long as you keep your Java installation version up to date). However, ensure that you periodically ask your producer about the schedule of upcoming certificate upgrades and expirations so that you are aware of the timeframe for testing out any new certificate. Keeping up to date on the schedule will help you avoid unnecessary license-server downtime when an old certificate expires. Practice To Avoid Because Revenera updates the FlexNet Operations Cloud SSL certificate annually, best practice is not to hard-code the hash of this certificate in your client code. With each certificate update, the hash changes. Additional Resource If you are using API to integrate your application with FlexNet Operations, see FlexNet Operations Cloud - Digital Certificates  for information about exporting and configuring SSL certificates from FlexNet Operations. 

Summary Revenera proactively communicates scheduled maintenance and important system related notices on the Revenera Status Dashboard. To know if your FlexNet Operations Cloud instance is impacted by an event announced on the status page, you must first understand the difference between the various FlexNet Operations Cloud editions and deployment environments and on which environment your instance is hosted. This article provides a brief description of the FlexNet Operations Cloud editions to better help you identify what updates are important to you. FlexNet Operations Cloud ALM vs LLM First, be aware that there are two editions of FlexNet Operations Cloud. FlexNet Operations Cloud ALM FlexNet Operations Cloud ALM (Advanced License Management) is Revenera’s entitlement management solution with a broader range of software monetization capabilities and deployment models. If you are accessing the FlexNet Operations Cloud producer portal using a URL similar to the following, then you are using FlexNet Operations ALM: https://<siteid>-fno.flexnetoperations.com/flexnet/operations For more details about the site ID and other FlexNet Operations Cloud ALM URLs, please refer to the FlexNet Operations Orientation Guide. FlexNet Operations Cloud LLM FlexNet Operations Cloud LLM (License Lifecycle Management) is Revenera’s original cloud-based entitlement management and software delivery solution. If you are accessing the FlexNet Operations Cloud Producer Portal using a URL similar to the following, then you are using FlexNet Operations LLM: https://manager.flexnetoperations.com/ For more details about FlexNet Operations Cloud LLM URLs, please refer to the in-app product documentation. FlexNet Operations Cloud Deployment Environments Below is a description of the deployment environments supported by Revenera. You will see references to these environments in the status dashboard notices. Location of the Deployment The following are the locations of the FlexNet Operations Cloud deployment environments: Data Center: Revenera-hosted and managed data center where FlexNet Operations LLM runs. Legacy AWS: Amazon cloud environment in both Europe (EU) and North America (NAM) that hosts FlexNet Operations ALM instances originally deployed in AWS.  AWS: Amazon cloud environment in both Europe (EU) and North America (NAM) that hosts new FlexNet Operations ALM instances and FlexNet Operations ALM instances migrated from the Data Center. Purpose of the Deployment The following describes the purpose of each of the FlexNet Operations Cloud deployment environments: UAT: User acceptance test environment used by testing pre-released builds of FlexNet Operations Cloud. In AWS NAM, FlexNet Operations ALM UAT is divided into three groups: UAT NAM1, UAT NAM2, and UAT NAM3. FlexNet Operations instances running in AWS NAM are assigned to one of these UAT groups. Production: Production environment of FlexNet Operations Cloud. In AWS NAM, FlexNet Operations ALM Production is divided into six groups: Production NAM1, Production NAM2, and Production NAM3, Production NAM4, Production NAM5, and Production NAM6. FlexNet Operations instances running in AWS NAM are assigned to one of these Production groups. PCS: Production Copy Service environment contains a copy of the production environment and is used for testing purposes. NOTE: PCS is a separate paid environment. Deployment environment support varies by FlexNet Operations Cloud variant. FlexNet Operations Cloud ALM Deployment Environments FlexNet Operations Cloud ALM is deployed on the following environments: Deployment Environments Data Residency Production Copy Service (PCS) User Acceptance Test (UAT) Production (PROD) Disaster Recovery (DR) AWS NAM US-West-2 (Oregon) X X X   AWS EU EU-West-1 (Ireland)   X X   Legacy AWS NAM US-West-2 (Oregon)   X X    Legacy AWS EU EU-West-1 (Ireland)   X X   FlexNet Operations Cloud LLM Deployment Environments FlexNet Operations Cloud LLM is deployed on the following environments: Deployment Environments Data Residency Production Copy Service (PCS) User Acceptance Test (UAT) Production (PROD) Disaster Recovery (DR) Data center California, US X X X   Illinois, US       X Considerations Your organization's FlexNet Operations ALM instance in AWS NAM is assigned to a particular group. You must subscribe to the group where your instance is hosted to receive status notifications. If you do not know the group your FlexNet Operations ALM instance has been assigned, contact Revenera Technical Support or your trusted Revenera contact for assistance. While FlexNet Operations LLM is hosted in the Revenera Data Center, it shares components with FlexNet Operations ALM that are hosted in AWS NAM. Specifically, these components are Device Activation Service and Cloud Licensing Service. If your FlexNet Operations LLM instance uses these components, to see the complete status of your FlexNet Operations LLM, you will need to subscribe to these components under your organization's assigned group. If you do not know the group your FlexNet Operations LLM components have been assigned, contact Revenera Technical Support or your trusted Revenera contact for assistance.

Introduction FlexNet Operations Cloud supports sending emails on behalf of your email server. For FlexNet Operations Cloud ALM hosted on AWS environments, Producers must first verify the email address/domain with AWS Simple Email Service (SES) to successfully send emails using the custom email address/domain. This article provides common troubleshooting steps in case an error is observed despite the verification process completing successfully. Troubleshooting Steps If using a custom email address/domain, please confirm that the DKIM information was added to your organization's DNS records by your IT team immediately after submitting the domain request. If after 48 hours, it is does not show validated, please contact Revenera Technical Support to request a review. Ensure the DKIM information remains in the DNS records throughout the life of the email address/domain. AWS SES may take 48-72 hours to detect the verified email address/domain.  If the email address/domain is verified in the Email/Domain Verification Tool, however it is not verified in the email template, try changing the email address in the template and then reverting it back. This will refresh the email template. Outcome If you continue to observe issues with sending emails using the custom email address/domain, please contact Revenera Technical Support for further assistance. Resolved Issue Note: The issue was resolved in FlexNet Operations ALM 2023.10 (deployed to Production on October 12, 2023 and UAT on October 15, 2023) There was a known issue with the domain verification process affecting migrated AWS UAT environments. When an custom domain is submitted for verification in the Email/Domain Verification tool of the FlexNet Operations Producer Portal, the generated DKIM records are incorrectly hard-coded with the flexerasoftware.com domain (see image below). Note: This issue does not affect custom email address verification. Workaround Note: The workaround is obsolete and users should discontinue its use. Please use the instructions in the Resolution section. When sharing the DKIM records with your IT team to add to your DNS records, you will need to replace the flexerasoftware.com domain with the custom domain. In the image above, you would replace flexerasoftware.com with revenera.com. Resolution The issue is no longer observed in FlexNet Operations ALM as of the 2023.10 release. Users should follow the instructions in the Verifying Email Addresses and Domains (AWS Only) of the FlexNet Operations User Guide -> Administrator Reference document and ensure the DKIM information is added to and maintained in your organization's DNS records. If you have any questions, contact Revenera Technical Support for assistance. More Information Refer to the Verifying Email Addresses and Domains (AWS Only) of the FlexNet Operations User Guide -> Administrator Reference document.

Introduction Revenera Status Dashboard displays real-time status and schedule maintenance information of Revenera cloud products. Users may subscribe to the dashboard to receive notifications about upcoming maintenance events and site outages.  This article provides instructions for subscribing to the Revenera Status Dashboard.  Instructions 1. On the Revenera Status Dashboard (https://status.revenera.com/), click the Subscribe to Updates button 2. Enter the email address where status notifications will be sent and click Subscribe Via Email 3. Optionally, you may subscribe to be notified by text message by clicking the phone icon and providing your phone number  4. Complete the captcha verification 5. Select the components you'd like to receive status notifications  6. Click Save at the bottom of the page More Information For information about the FlexNet Operations Cloud environments, please refer to the Understanding the FlexNet Operations Cloud Editions and Deployment Environments article.

Question Where can users find Amazon Web Services (AWS) security documents? Answer Amazon's security documentation, including their SOC (System and Organization Controls) 2 Type II report, is available via the AWS Artifact service. AWS account administrators can download the report using this self-service tool. If you do not have an AWS account, you will need to register for an account to access the report.  The reports from AWS Artifact are watermarked with the account they are downloaded from and sharing the document outside the of the registered account is not permitted. More Information For more information about AWS SOC Compliance reports and how to registered an account on AWS Artifact Service, please refer to the following resources: https://aws.amazon.com/compliance/soc-faqs/ https://aws.amazon.com/artifact/getting-started/

Introduction Reidentifying members results in the following error (LLM): Cannot add Member ID <memberID> to Member with Email address <email> since this member already has a Member ID. The issue is with the existing multiple Member IDs. Solution You must delete one or both member IDs before you can add/update the new ID. Do the following: Open the Reidentify page, select one of the IDs in the dropdown, leave the new Member ID field blank and click Submit. You should now only have 1 Member ID. The normal reidentifying process should work as expected. If you still encounter issues, also delete the second old ID and then go back and add the new one. Outcome Only one Member ID is present for the member.

Question Is there any way we can set the Default server port number in the license file while generating or Activating the FNP license file under Flexnet Operations (FNO) Answer The Default server port number can be configured in the License generator configuration under Custom Attribute value  --> Default server port number in the license file while configuring the VCG.  More Information This configuration can set the default port of the license server however this can be updated to a different port if required.

Introduction Language issues on the End-user Portal for downloads when using Out of the box language property file.   One of the reasons that caused this issue was seen in the customized jsp provided by the client. We could see that there are single quotes in line onload="executeOnLoad('${noRecords}', '${noEntitlements}');"   Troubleshooting Steps   Go to path of portalStart.jsp location, \operationsportal\portalStartPage.jsp from FNO installation from client. Edit using Notepad and modify the below line: </select> <img class="spinner" src="${appContextPath}/resources/operationsportal/spinner.gif" onload="executeOnLoad(&quot;${noRecords}&quot;, &quot;${noEntitlements}&quot;);"> 3. Save the file.         4. Refresh the UI page and the change should be reflected.   More Information You can make this change while FNO is running, no need to redeploy since its a jsp change.