Driver_Girl Frequent Contributor.
Frequent Contributor.
1236 views

Designer 4.7 Changes drivers in view when I open a policy

I am not even sure how to describe this, but here it goes. I will open designer and infront of me I will have the drivers on the right and the list view on the left. I will pick a driver to work on example ABC driver, then on the left side I will pick the fishbone outline, all is good at this point. Then I will pick a policy from the event transform to open, then when it opens the driver in the fishbone will change to the last driver that was opened. So you are working on the correct policy on the right but on the left a different driver with different policies. I have tried to open more policies and do saves the the driver on the left always changes.

Any help would be appreciated.

Sheryl
Labels (1)
0 Likes
20 Replies
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a policy

On 3/27/2019 2:44 PM, Driver Girl wrote:
>
> I am not even sure how to describe this, but here it goes. I will open
> designer and infront of me I will have the drivers on the right and the
> list view on the left. I will pick a driver to work on example ABC
> driver, then on the left side I will pick the fishbone outline, all is
> good at this point. Then I will pick a policy from the event transform
> to open, then when it opens the driver in the fishbone will change to
> the last driver that was opened. So you are working on the correct
> policy on the right but on the left a different driver with different
> policies. I have tried to open more policies and do saves the the
> driver on the left always changes.


This was a new bug in 4.7 and I have not seen repeating in 4.7.2 so
might consider updating.




0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Designer 4.7 Changes drivers in view when I open a policy

Geoffrey Carman,

>>
>> I am not even sure how to describe this, but here it goes.  I will open
>> designer and infront of me I will have the drivers on the right and the
>> list view on the left.  I will pick a driver to work on example ABC
>> driver, then on the left side I will pick the fishbone outline, all is
>> good at this point. Then I will pick a policy from the event transform
>> to open, then when it opens the driver in the fishbone will change to
>> the last driver that was opened.  So you are working on the correct
>> policy on the right but on the left a different driver with different
>> policies.  I have tried to open more policies and do saves the the
>> driver on the left always changes.

>
> This was a new bug in 4.7 and I have not seen repeating in 4.7.2 so
> might consider updating.
>


A new bug? I see the same behavior in Designer 4.6.2 and I could swear
it was in the previous version (4.5.5?) too. I've learned to just grit
my teeth and change it back every time it switches on me.




0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a policy

On 3/27/2019 3:20 PM, 6423241 wrote:
> Geoffrey Carman,
>
>>>
>>> I am not even sure how to describe this, but here it goes.  I will open
>>> designer and infront of me I will have the drivers on the right and the
>>> list view on the left.  I will pick a driver to work on example ABC
>>> driver, then on the left side I will pick the fishbone outline, all is
>>> good at this point. Then I will pick a policy from the event transform
>>> to open, then when it opens the driver in the fishbone will change to
>>> the last driver that was opened.  So you are working on the correct
>>> policy on the right but on the left a different driver with different
>>> policies.  I have tried to open more policies and do saves the the
>>> driver on the left always changes.

>>
>> This was a new bug in 4.7 and I have not seen repeating in 4.7.2 so
>> might consider updating.
>>

>
> A new bug? I see the same behavior in Designer 4.6.2 and I could swear
> it was in the previous version (4.5.5?) too. I've learned to just grit
> my teeth and change it back every time it switches on me.


Ok, it was there. BUt I think they finally fixed it.

Side note: Does your project name have a space in it (In the Projects
view?) If so, rename away the space post haste.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Designer 4.7 Changes drivers in view when I open a policy


>> Geoffrey Carman,
>>


>>
>> A new bug? I see the same behavior in Designer 4.6.2 and I could swear
>> it was in the previous version (4.5.5?) too. I've learned to just grit
>> my teeth and change it back every time it switches on me.

>
> Ok, it was there. BUt I think they finally fixed it.
>
> Side note: Does your project name have a space in it (In the Projects
> view?)  If so, rename away the space post haste.
>
>


No spaces, just alphanumerics and one underscore.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a policy

On 3/27/2019 4:15 PM, 6423241 wrote:
>
>>> Geoffrey Carman,
>>>

>
>>>
>>> A new bug? I see the same behavior in Designer 4.6.2 and I could
>>> swear it was in the previous version (4.5.5?) too. I've learned to
>>> just grit my teeth and change it back every time it switches on me.

>>
>> Ok, it was there. BUt I think they finally fixed it.
>>
>> Side note: Does your project name have a space in it (In the Projects
>> view?)  If so, rename away the space post haste.
>>
>>

>
> No spaces, just alphanumerics and one underscore.


Underscores and dashes are fine, it is spaces that makes everything go
wonky. Like really wonky. Try it, it is bad.

0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a polic

geoffc;2497468 wrote:
On 3/27/2019 4:15 PM, 6423241 wrote:
>
>>> Geoffrey Carman,
>>>

>
>>>
>>> A new bug? I see the same behavior in Designer 4.6.2 and I could
>>> swear it was in the previous version (4.5.5?) too. I've learned to
>>> just grit my teeth and change it back every time it switches on me.

>>
>> Ok, it was there. BUt I think they finally fixed it.
>>
>> Side note: Does your project name have a space in it (In the Projects
>> view?)Â* If so, rename away the space post haste.
>>
>>

>
> No spaces, just alphanumerics and one underscore.


Underscores and dashes are fine, it is spaces that makes everything go
wonky. Like really wonky. Try it, it is bad.


It's *more* wonky with a space in the name, but this behaviour isn't new. Designer has long had a misfeature in how it manages its various panels within the interface. The outline/fishbone view really wants to reset itself to outline, regardless of what you want it to do. The model wants to scroll to what it thinks you want to see, regardless of what you think you wanted. The Policy Set view randomly tries to follow what the Outline tab is doing, but often shows something else unexpected entirely.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a policy

>>> No spaces, just alphanumerics and one underscore.
>>
>> Underscores and dashes are fine, it is spaces that makes everything go
>> wonky. Like really wonky. Try it, it is bad.

>
> It's *more* wonky with a space in the name, but this behaviour isn't
> new. Designer has long had a misfeature in how it manages its various
> panels within the interface. The outline/fishbone view really wants to
> reset itself to outline, regardless of what you want it to do. The model
> wants to scroll to what it thinks you want to see, regardless of what
> you think you wanted. The Policy Set view randomly tries to follow what
> the Outline tab is doing, but often shows something else unexpected
> entirely.


So some of the problem is that to support version control, they made
every editor tab (a Policy, a Resource, a Mapping Table) that you open
have its own entire copy of the entire project in memory.

Now this seems intensely ill advised.

Some of the downsides:
- Kill performances
- Eats memory
- If you dirty one tab, forget to save, move to second, you have to
throw away one change. They are independent copies, and as you save one
you overwrite the other change.
- When you switch tab to tab, the Outline view in independent of the
previous one, so persisting a consistent view is probably not going to work.

Upside:
- Gets SVN working, sort of, poorly.

So because of all the copies of the project in memory, every Outline tab
has a different state. So when you go from tab to tab, you see the
different states.

Very annoying and I wish they could figure out how to fix it.


0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a polic

geoffc;2497473 wrote:
>>> No spaces, just alphanumerics and one underscore.
>>
>> Underscores and dashes are fine, it is spaces that makes everything go
>> wonky. Like really wonky. Try it, it is bad.

>
> It's *more* wonky with a space in the name, but this behaviour isn't
> new. Designer has long had a misfeature in how it manages its various
> panels within the interface. The outline/fishbone view really wants to
> reset itself to outline, regardless of what you want it to do. The model
> wants to scroll to what it thinks you want to see, regardless of what
> you think you wanted. The Policy Set view randomly tries to follow what
> the Outline tab is doing, but often shows something else unexpected
> entirely.


So some of the problem is that to support version control, they made
every editor tab (a Policy, a Resource, a Mapping Table) that you open
have its own entire copy of the entire project in memory.

Now this seems intensely ill advised.

Some of the downsides:
- Kill performances
- Eats memory
- If you dirty one tab, forget to save, move to second, you have to
throw away one change. They are independent copies, and as you save one
you overwrite the other change.
- When you switch tab to tab, the Outline view in independent of the
previous one, so persisting a consistent view is probably not going to work.

Upside:
- Gets SVN working, sort of, poorly.

So because of all the copies of the project in memory, every Outline tab
has a different state. So when you go from tab to tab, you see the
different states.

Very annoying and I wish they could figure out how to fix it.


I agree with everything, except SVN. From what I recall, this was true before SVN support was added. Each tab has always been its own in-memory copy of the whole project. Each tab, if "dirty", must be saved before any other tab gets "dirty", otherwise you're going to lose some (or both) changes, and the results are unpredictable.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a policy

On 3/28/2019 3:16 PM, dgersic wrote:
>
> geoffc;2497473 Wrote:
>>>>> No spaces, just alphanumerics and one underscore.
>>>>
>>>> Underscores and dashes are fine, it is spaces that makes everything

>> go
>>>> wonky. Like really wonky. Try it, it is bad.
>>>
>>> It's *more* wonky with a space in the name, but this behaviour isn't
>>> new. Designer has long had a misfeature in how it manages its various
>>> panels within the interface. The outline/fishbone view really wants

>> to
>>> reset itself to outline, regardless of what you want it to do. The

>> model
>>> wants to scroll to what it thinks you want to see, regardless of what
>>> you think you wanted. The Policy Set view randomly tries to follow

>> what
>>> the Outline tab is doing, but often shows something else unexpected
>>> entirely.

>>
>> So some of the problem is that to support version control, they made
>> every editor tab (a Policy, a Resource, a Mapping Table) that you open
>> have its own entire copy of the entire project in memory.
>>
>> Now this seems intensely ill advised.
>>
>> Some of the downsides:
>> - Kill performances
>> - Eats memory
>> - If you dirty one tab, forget to save, move to second, you have to
>> throw away one change. They are independent copies, and as you save
>> one
>> you overwrite the other change.
>> - When you switch tab to tab, the Outline view in independent of the
>> previous one, so persisting a consistent view is probably not going to
>> work.
>>
>> Upside:
>> - Gets SVN working, sort of, poorly.
>>
>> So because of all the copies of the project in memory, every Outline
>> tab
>> has a different state. So when you go from tab to tab, you see the
>> different states.
>>
>> Very annoying and I wish they could figure out how to fix it.

>
> I agree with everything, except SVN. From what I recall, this was true
> before SVN support was added. Each tab has always been its own in-memory
> copy of the whole project. Each tab, if "dirty", must be saved before
> any other tab gets "dirty", otherwise you're going to lose some (or
> both) changes, and the results are unpredictable.


Perhaps, my recollection is that this was done for SVN support.
Something of a angels on the head of a pin at this point though.

Be nice to see it fixed though.


0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a policy

dgersic wrote:

> Each tab, if "dirty", must be saved before
> any other tab gets "dirty", otherwise you're going to lose some (or
> both) changes, and the results are unpredictable.


Only if you edit the same object in both tabs. The last save wins in that case,
so it's not entirely unpredictable, just annoying and not very obvious. If you
edit different objects in both tabs, one will not see the change made in the
other until you close and reopen.

I find the message box most confusing that informs about changes saved in first
tab when you switch to the next "dirty" one and asks if you want to "reload" or
"ignore". If you hit "reload" unsaved changes in this tab are lost, so always
hit "ignore", then save the tab and close/reopen to also see the changes saved
in the first tab.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a polic

lhaeger;2497524 wrote:
dgersic wrote:

> Each tab, if "dirty", must be saved before
> any other tab gets "dirty", otherwise you're going to lose some (or
> both) changes, and the results are unpredictable.


Only if you edit the same object in both tabs. The last save wins in that case,
so it's not entirely unpredictable, just annoying and not very obvious. If you
edit different objects in both tabs, one will not see the change made in the
other until you close and reopen.

I find the message box most confusing that informs about changes saved in first
tab when you switch to the next "dirty" one and asks if you want to "reload" or
"ignore". If you hit "reload" unsaved changes in this tab are lost, so always
hit "ignore", then save the tab and close/reopen to also see the changes saved
in the first tab.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)


From what I recall, and it's been a while, your choices there are:

"Reload" - discards the changes in this tab and reloads the in-memory image of the project. So you lose what you were doing in this tab.

"Ignore" - ignores the changes on disk, so that when you save this tab, you lose what you were doing in the *other* tab.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a policy

dgersic wrote:

> "Ignore" - ignores the changes on disk, so that when you save this tab,
> you lose what you were doing in the other tab.


.... only if its saved in a file also edited in the other tab, so usually only
if you edited the same object in both tabs. "Reload" makes you loose something
for sure, "Ignore" only in rare cases. I wonder what exactly happens when you
hit the "Save All" button and there's a potential conflict...

Anyway, I guess we can agree on the best practice: always save before editing
something in another tab.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a polic

lhaeger;2497567 wrote:
dgersic wrote:

> "Ignore" - ignores the changes on disk, so that when you save this tab,
> you lose what you were doing in the other tab.


.... only if its saved in a file also edited in the other tab, so usually only
if you edited the same object in both tabs. "Reload" makes you loose something
for sure, "Ignore" only in rare cases. I wonder what exactly happens when you
hit the "Save All" button and there's a potential conflict...

Anyway, I guess we can agree on the best practice: always save before editing
something in another tab.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)


I learned early on never to let two tabs get dirty. What happens when that happens now, I don't know. I got tired of losing work, and learned to prevent it from happening.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Designer 4.7 Changes drivers in view when I open a policy

On 4/2/2019 2:26 PM, dgersic wrote:
>
> lhaeger;2497567 Wrote:
>> dgersic wrote:
>>
>>> "Ignore" - ignores the changes on disk, so that when you save this

>> tab,
>>> you lose what you were doing in the other tab.

>>
>> .... only if its saved in a file also edited in the other tab, so
>> usually only
>> if you edited the same object in both tabs. "Reload" makes you loose
>> something
>> for sure, "Ignore" only in rare cases. I wonder what exactly happens
>> when you
>> hit the "Save All" button and there's a potential conflict...
>>
>> Anyway, I guess we can agree on the best practice: always save before
>> editing
>> something in another tab.
>>
>> --
>> http://www.is4it.de/en/solution/identity-access-management/
>>
>> (If you find this post helpful, please click on the star below.)

>
> I learned early on never to let two tabs get dirty. What happens when
> that happens now, I don't know. I got tired of losing work, and learned
> to prevent it from happening.


And you get that "Oh crap" moment when you realze you have just done it.

Then I compare, snag the diffs into a text file, close without saving
the second tab, save the first, then go redo the changes.

Hate when that happens.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.