How to work around a download bug on the Forge.

How to work around a download bug on the Forge.

  

All,

We have had a case open since the 7th of June about a issue where a forge component doesn't install or upgrade when you hit the install after all the validations have been completed successfully. Installs and upgrades perfectly fine if you download from the forge. Support haven't been able to remedy and we have asked support to delete the forge entry previously so we can recreate it, but they can't. Deactivating just reactivates as soon as we try to create a new entry.  

Does anyone know if we recreate the app from a clone if that will definitely result in a new forge entry? We presume also that anyone downloading the new version will have to migrate data across as the App will have a new 'id'.

Thanks


Paul,

Is this related to a specific forge component or any forge component?

Also, which version of ServiceStudio are you using?

Ouen

Ouen Worth wrote:

Paul,

Is this related to a specific forge component or any forge component?

Also, which version of ServiceStudio are you using?

Ouen

Ouen,


The component is this one.  

https://www.outsystems.com/forge/component/3875/raisers-edge-permission-and-consent-interface/

always the latest version of Service Studio


Paul Davies wrote:

Ouen Worth wrote:

Paul,

Is this related to a specific forge component or any forge component?

Also, which version of ServiceStudio are you using?

Ouen

Ouen,


The component is this one.  

https://www.outsystems.com/forge/component/3875/raisers-edge-permission-and-consent-interface/

always the latest version of Service Studio


Hi Paul,

Download the component, and install Via Service Center:



And check in your 

Environment Health 
 if you have any error


When you publish via ServiceCenter any issues with the modules or dependencies will be indicated.

There may be an issue with the Silk UI or Dublin versions that it is dependent on and you will see that in the publish log.

Fábio Vaz wrote:

Paul Davies wrote:

Ouen Worth wrote:

Paul,

Is this related to a specific forge component or any forge component?

Also, which version of ServiceStudio are you using?

Ouen

Ouen,


The component is this one.  

https://www.outsystems.com/forge/component/3875/raisers-edge-permission-and-consent-interface/

always the latest version of Service Studio


Hi Paul,

Download the component, and install Via Service Center:



And check in your 

Environment Health 
 if you have any error


Fabio,

People have been using this workaround for last couple of weeks. Ideally the component would install as per the normal forge workflow. 

Paul, 

Of course, but instead we have that solution.

Ouen Worth wrote:

When you publish via ServiceCenter any issues with the modules or dependencies will be indicated.

There may be an issue with the Silk UI or Dublin versions that it is dependent on and you will see that in the publish log.

Using the latest version of Silk UI and Dublin.  We have no issues with the other  8 or so modules we have published.


We have just received a note from OS support that a patch is being released 26th June 2018 to correct for the bug leading to the forge install issue.

OutSystems released a patch yesterday to the forge code to address the issue but early testing indicates that it hasn't fixed the bug.  We have sent this feedback to Support for further investigation.

 

OutSystems have now resolved the Forge issue.  Module is installing cleanly from developer studio.