Log in to AnswerLog in to Follow
Igor Kirtak
206Views
12Comments
Solved
[OutSystems UI] Not visible in LifeTime
Question
Forge
OutSystems UI
Forge component by OutSystems R&D

Hi,

We a working on pushing our code to the new environment, and the problem is that OutSystems UI is not available to choose in LifeTime. It is also not shown in Service studio. At the same time, OutSystems UI Web is shown.

Is this by design? What is the process to ensure that the same version is present on all environments? Is there something in data which can be tweaked to make it available in LifeTime (I have checked in Application entity and don't see any difference from other apps)?

0
0
on 2020-05-06
Tiago Bernardo
Champion
Solution

Hi all!

This is a very annoying bug in LifeTime that I have reported previously to OutSystems back in November 2019 but until now it has not been fixed.

It has been filled as ID "RPD 4774", and I was told to keep checking LifeTime Release Notes.

The issue is that new versions of components/applications (system and forge) that have a different name (but also different description and icon) will not synchronize correctly to LifeTime, so in Service Center (and Service Studio) of the environment they will appear with the new name but in LifeTime they still appear with the old name.

For forge components, there is a workaround which is to just make a small change in the description (or the name) of the application, and LifeTime will detect there is a change in the application and synchronize it correctly. (of course, with this small change the component becomes customized and not possible to be automatically updated, but what I do is just reinstall manually the latest version of the component).

But, for system components, like "OutSystems UI", it is impossible to rename the application or make any kind of change, so it is not possible to "trigger" LifeTime to make a successful synchronization.

This a summary of the main system components that have been renamed:

Example of the problem for "Charts Mobile", now called "OutSystems Charts".

Service Center (OK):

Service Studio (OK):

LifeTime (NOK):

--Tiago Bernardo

See solution in context
4
0
on 

Tiago Bernardo Many thanks for this! Now I was able to find it under the name "Silk UI Mobile".

0
0
on 2020-05-07
Daniël Kuhlmann
mvp_badge
MVP

Hi Igor,

Are LifeTime roles & teams being used for the different LifeTime users?

If so it could be that the person does not have the proper permission to deploy the component to the target environment.

The process to have the same version in all environments is to push them from dev to test to qa to prod.

Regards,

Daniel

0
0
on 2020-05-06

Daniël Kuhlmann wrote:

Hi Igor,

Are LifeTime roles & teams being used for the different LifeTime users?

If so it could be that the person does not have the proper permission to deploy the component to the target environment.

The process to have the same version in all environments is to push them from dev to test to qa to prod.

Regards,

Daniel

Several people were checking this. As far as I know all of them having maximum permissions. I myself am Administrator role, which is the highest. Other applications are available, including Outsystems UI Web. Ousystems UI seems to be the only one missing.

I have also checked in the list of applications returned by Life Time API - it's not there also.

"push them from dev to test" :) How exactly? With LifeTime or somehow else? Do you have it shown in LifeTime?

0
0
on 2020-05-06
Daniël Kuhlmann
mvp_badge
MVP

Hi Igor,

I checked on one of our customer infrastructures, and to my supprise experience the same issue with OutSystems UI application. It is in DEV but not visible in LifeTime.

I will try and find out what can explain this. If needed I contact OutSystems.

Regards,

Daniel

1
0
on 2020-05-06
Daniël Kuhlmann
mvp_badge
MVP

Hi Igor,

I did some investigation what is happening, this is my conclusion sofar:

  1. Originally only OutSystems UI Mobile existed, prior to the availability of Reactive Web app.
  2. Then Reactive Web applications and OutSystems UI where introduced.
  3. The OutSystems UI Mobile app was renamed to OutSystems UI, as it uses the same foundation (module OutSystemsUI).
  4. Deploying the DEV modules to TST and other environments, for reason I don't understand, did not rename the application. So in DEV it is called OutSystems UI, but in TEST, QA etc it is still called OutSytems UI Mobile.

If I filter on OutSystems UI Mobile in LifeTime it does list the 2 components part of OutSytems UI in DEV, why? 

I will ask feedback from OutSystems on this, as it is strange to see a module in 1 environement in application X and in another in application Y. and if X and Y are the same application when then different names per enviroment.

I will keep you posted.

Regards,

Daniel 

0
0
on 2020-05-06
J.
mvp_badge
MVP

For service studio you should check preference to make sure


1
0
on 2020-05-06

J. wrote:

For service studio you should check preference to make sure


This is nice, thanks! However doesn't solve the problem... One option we were considering was to move those modules to own own application. But they don't have the "move" button.


0
0
on 2020-05-06
Tiago Bernardo
Champion
Solution

Hi all!

This is a very annoying bug in LifeTime that I have reported previously to OutSystems back in November 2019 but until now it has not been fixed.

It has been filled as ID "RPD 4774", and I was told to keep checking LifeTime Release Notes.

The issue is that new versions of components/applications (system and forge) that have a different name (but also different description and icon) will not synchronize correctly to LifeTime, so in Service Center (and Service Studio) of the environment they will appear with the new name but in LifeTime they still appear with the old name.

For forge components, there is a workaround which is to just make a small change in the description (or the name) of the application, and LifeTime will detect there is a change in the application and synchronize it correctly. (of course, with this small change the component becomes customized and not possible to be automatically updated, but what I do is just reinstall manually the latest version of the component).

But, for system components, like "OutSystems UI", it is impossible to rename the application or make any kind of change, so it is not possible to "trigger" LifeTime to make a successful synchronization.

This a summary of the main system components that have been renamed:

Example of the problem for "Charts Mobile", now called "OutSystems Charts".

Service Center (OK):

Service Studio (OK):

LifeTime (NOK):

--Tiago Bernardo

4
0
on 2020-05-07

Tiago Bernardo Many thanks for this! Now I was able to find it under the name "Silk UI Mobile".

0
0
on 2020-05-07
Daniël Kuhlmann
mvp_badge
MVP

Thanks Tiago, that is valuable information.

0
0
on 2020-05-07

In our case, we download the Outsystems UI from DEV and publish in Qa, after that the Outsystems UI Mobile become Outsystems UI

0
0
on 2020-10-30

Hi all, I have the same issue with OutSystem UI not showing up in LifeTime as an application that I can deploy. Therefor I downloaded it from DEV and uploaded in QA. In ServiceCenter I see this is done correctly, but the application is still not showing up in LifeTime. How come?

The difference with the situation of Carlos might be that I didn't have OutSystems UI Mobile on QA yet. We are working on the first mobile app for this customer. Anyone a suggestion how to go ahead? Keep on using Service Center for the deploy of OutSystems UI? Also to Production?

0
0
on 2020-12-03

For future reference I posted another way to fix this without having to change the name/description: https://www.outsystems.com/forums/discussion/71180/workaround-fix-to-lifetime-application-name-bug/

0
0
2 days ago
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.