0
 Followers
2
 Likes

Assertiveness in changed objects indicator in Service Studio

Aggregates & Queries
Out of the scope

Hi.


Ignore "View Data" action (and others can be exists) like change indicator of an object/module.

I believe this makes perception more assertive of "real changes" maded.

Created on 11 Sep 2018
Comments (5)

Hey Maycon,

Not sure if I understood. Can you provide more details or perhaps some image/screenshot?

Cheers

Hi Vasco.


Simple operation in SS like "View Data" flag object status changed and its represent (to IDE) that a modification, but is not real.
Its can be ignored to not "disturb" about modified objs.

Upgrading...

We don't accept this a "real change".

Hey Maycon,

Got it! The reality is that, to show you the View Data, we create a simple aggregate that is than stored in the oml so that you can use it later (e.g. in other Service Studio sessions).

To do that, we need to flag a change to the oml (because it has indeed changed).

I know this is not obvious but the alternative would be not storing it and you would lose the view data from a session to another.

Cheers,

Changed the category to Aggregates & Queries and the status to

Out of the scope


Hey Maycon,

As explained this is necessary to persist the change in the module so that you have the same view data, filters and sorts when reopening Service Studio.

Because of this, we don't have plans to do this.

Cheers,

views
276
Followers
0