Thank you very much Ricardo. I was working late, and I was already feeling tired.

Best regards,

Nuno Miguel Verdasca

Hi, Miguel

We've been tweaking the experience in pages where publish occurs (modules, apps, solutions) according to the feedback we're received. In Service Center's latest version (Platform Server 11.8.0) we've added a progress bar to these pages, as you can see in the example below:

What do you think about this? 

Best regards,

Rita Tomé

Hi Rita,

I think it helps when we are making a publication, to have a greater perception of where we are and how much more to finish.

A question, also in this new version of the service center, each time a step ends, the information for that step is collapsed. And in my opinion it is another very positive point. I ask what do you think of one of this two suggestions:

•  instead of progressing downwards, reversing growth ... that is, the last step to happen is the first on the list, or ...
• as the page grows, there is a scroll down to accompany its growth ...

Rita, these are just suggestions. =)

Cheers,
Miguel Verdasca

I think the progress bar is indeed an improvement. Doest the platform know how many steps in total are to be executed? Because know the list just keeps getting longer, without you knowing how long it will be. If we know in advance that the list has 100 records, then it actually means something when we are at 30% of the steps.

Miguel,
Suggestions are always welcome :) Why do you feel the need to invert the list or to have an automatic scroll? Do you still have to scroll a lot after these changes?


Kilian,
So, what you're saying is that you need to see the list of all steps to have a clear notion of the time the publish will take, is that it?

Hi Rita,
I have already seen the progress bar in the service center in my personal area and it is very cute. What Kilian mentions is part of my initial idea, so that we have a more precise notion. But as long as this progress bar is more or less aligned with the progress time, I no longer "complain".

If you have small applications, no, but if you have large applications like the ones I have, you have to do a lot of scrolling. After we reach the bottom of the page and have seen what we want, we have to scroll all the way up to see if the deployment is still in progress or not.

I honestly don't know RIta, I'm sure you'll have more experience than me, but is that too difficult to implement ?

Hi all!

But I really appreciated that you collaborated in the discussion of the idea, sharing your opinion about the need for it, and that other topics related to the idea could contribute.

Thank you all for your support.

Hi, Miguel

I wasn't asking those questions because inverting the log is too difficult to implement, but because I was trying to understand the problem you were facing :) Before implementing a solution, we need to understand clearly the need so that we can be sure that we're solving it.

Thanks for all your input!

I understand that it is complicated, to have that progress bar, and if you have a percentage of what you have already done or an example, performed 5 tasks out of 12, it helps a lot.

Invert actually helps, for example, sometimes the publication blocks, we continue to see the wheel spinning indicating that it is progressing, but in fact there is a message asking if we want to continue or abort ... how many times have you been "tricked "in this situation (",) :) I think I was deploying and after all, waiting for my action!

Inverting we always know what is going on, or instead of inverting, put the page to scroll down while advancing. This would be very useful and countless people agree with this idea, I do not speak here, but I speak on a daily basis, but if they think it will be something that the effort is immense I understand.

If it is not possible to do this, at least place these cases in which there is a need for intervention, these messages and buttons are placed in the upper area.