Infor OS Portal Trial Mode for Multi Tenant Customers

Hello Noe! We are experiencing the same thing with the browser back button not working. I did confirm with Infor they are aware of the issue and currently deciding how to make it behave (i.e. switching between tabs or browsing back on the current tab, option two being my vote). The only other issue I have noticed is opening bookmarks. It appears sometimes they open under a new workspace and other times they open under the already open workspace.

Other than that it's been a good experience.

glad to hear it's not just us. with more reporting the same issue hopefully it's able to be resolved. i do agree on the back button should be taking you back on the current tab.

So far that's the only thing we've noticed but will continue working within it daily.

After using the new OS Portal and experiencing how the back button works with the tabs, I've stopped using it. Instead, I just open a new browser tab, like I've done in the past.

If they don't fix it so that the back button takes you back on the current tab, I don't see our users adopting the new tabs.

Rebecca Derr

For me the back button is the only frustrating thing I've experienced. Other than that, it's been pretty nice. I use the new portal exclusively now.

Totally agree. Our users will continue to open multiple tabs in the browser until and unless the browser back button is configured to go back in the workspace, not switch between.

We agree. That's our top frustration. We'd like the back button to work within the workspace. Other than that we are happy with the OS Portal.

Do we know if this is going to change or if a different solution is coming down the pike? We will be rolling this out to a much wider user group following the October CU and we know this is going to be a big dissatisfier. It has the potential to offset all of the good because when using multiple workspaces, as all users do, the back button is going to just bounce them back to their most recent workspace when you want to go back within the current workspace. Since we can't do that now we have to start over within the menu to get back to a list view or form for next steps. Even just a breadcrumb trail at the top of the page that is clickable would be better.

Infor??? This is the biggest rock in our shoe with Portal and we'd like to see a fix for it before we put all of our users in it. Other than that we are really enjoying it.

Heidi Anderson

Upvoting -- St. Luke's Health System has the same frustration point; without the functioning back button, users will continue to have several browser windows open, which doesn't really feel like an enhancement

I have an incident open with Infor and we are working to sync up to have a shared session for them to do some more testing. If we all open tickets then i'm sure that will help push a fix to come out soon for it. If i have any updates from my incident i'll be sure to follow up with a reply here.

Good morning all! I just completed my shared session with Infor to help them understand the back button issue. They were able to see exactly the issue in our recorded session and said they would take it back to the dev team. I did tell them others in the community had the same issue and infor did agree in everyone opening up incidents with your organization for this issue to help the dev team see how much of a priority it is to get this fixed. In my call today i told them this issue alone would be important enough for me to believe if not fixed by their April 2024 deadline it would need to be pushed back or not made mandatory for everyone to move.

my incident for this in case anyone needs to reference is 17721040

Thanks for the update, Noe.

I just entered an incident to support this fix as well. Incident 17777248.

Ticket 17781880 just entered requesting the same.

Hans Mueller

Hi all -

The OS Portal product development team would like to arrange a call with a group of customers to talk further about these concerns. Can you please email me (hans.mueller@infor.com) or reply here on this thread if you are interested in joining that call, and what blackout dates next week you have?

Thanks,

Hans

Ray Juodis

Morning Hans - Please add me to your call. Thanks - Ray

Would be happy to join that call as well. Thanks Hans.

andy

What was the consensus from this call? Is it possible for Dev to fix this browser back issue in the portal, and if so is it targeted to be fixed in a future release?

On a related note, did anyone else see in the Jan 24 CU release notes that PORTAL-USER role is no longer required to gain access to OS Portal when in trial mode ? This means you cannot control access to OS Portal. All of our PP1 non PORTAL-USER role holders can access OS Portal now, another update is that they have a "Try OS Portal" button in the upper right corner of Mingle now which spawns a new tab to v2 mode.

NOT GOOD.

i haven't read that far in advance yet but will do so now.

it's my understanding that the OS portal conversion can be postponed to not take place in April on the original scheduled date and can be pushed back as far as the October release. It requires you to send an email to your account rep manager and let them know

You may want to check that. All of our tenants are in trial mode. This update in the release notes specifically mentions trial mode.

I have entered an incident on this and will report back what they say. Also, following up with our CSM.

i understand this to be a toggle in the admin settings - so i take it as with the removal of the system 'checking for selected portal-user security role' assigned to the user - and if the toggle it a off/on for all users - then this can no longer be controlled at a one by one basis and if enabled it becomes possible that anyone within the organization can do the 'try now' button.

i would be curious to know if once a user clicks on the 'try now' button if that then enabled the new version as a 'default' or if it's only opened/launched when clicked on leaving the default as it is today?

Confirm there is a Try the new OS Portal label in the Portal bar when it has been enabled from the Admin Settings.

Confirm that when clicked, OS Portal will launch in a new browser tab

latest update from Infor is they are not going to allow anyone to postpone the new OS version. It's going to happen with the April release and as of today they have not fixed the back button issue.

@Infor I can't stress enough how big of an issue this is. I've had a ticket opened for 4 months and haven't heard anything about a solution coming. Can we get an update on this? This single issue will outweigh all of the positive improvements delivered in OS Portal.

hatem-elkhashab

Actually, I have a question about that. I understand they will not allow delay of migration, but are they planning to force everyone to enable(toggle) the new features to all user groups?

And if you are currently on trial mode, the dependence on having the PORTAL-USER role to gain access to V2 is removed in the January CU. So, technically it is available to all mingle users when the Jan CU is released in your PRD environment.

dbrucke1

Mark yes there is a button that will be released in January but you do have the option to turn it off so if you don't want your employee to access it yet you can. There is a KB article that shows how to do it and is fairly simple to follow and it will remove the button so you users do not have access to OS Portal.

that's correct. Then once the April CU comes then that button will go away and the new OS will be the only option. There is an event announcement coming up related to this that may be helpful to attend. i just registered today and curious.

if anyone wants the register links let me know and i can copy and paste them here if you have not received this document yet.

lviar

Yes, please post links. Thank you.

Rebecca Schaeffer

Our back button in DEV V2 works.

Hi Rebecca - We use V2 as well. Are you saying that the back button works within each workspace? The issue we're discussing is the back button doesn't work as expected within each workspace. Current functionality, the back button moves us back through each click like a normal webpage rather than keeping us within the selected workspace we want to go to the previous page in.

Rebecca Schaeffer

Thank you for meeting with me today Stace. The back button is NOT working as expecting when moving from one workspace to another. I too am hoping Infor can get this figured out before the April CU.

cleverly

@hans-mueller

It's been over three weeks since Andy asked his question (albeit over the holidays, so potentially missed); any chance we can get an answer to his astute question? If, for example, it isn't even technically possible for Dev to do anything then that would be good to know.

Hans Mueller

Hi all -

Good afternoon. Regarding the April deadline and rumors of a delay/postponement, here is the official word from Infor. If you have questions, please feel free to reach out to your CSx or to myself surrounding this process outlined below:

-------------------------------------

Infor has not extended the date for required transition from Ming.le to OS portal by April 30, 2024. In the event there are extenuating circumstances making the transition unobtainable by the deadline, there may be an exception granted if one or more of the following criteria exist:

Validated application bug as a result of running in OS Portal TRIAL mode impacting use
Validated OS Portal bug that prevents customer from conducting business
Go Live within 60 days of cutover
Special Circumstance: To be considered by approver

There are two levels of approval required for considered exceptions. A support incident is needed to request an exception with details of the request including expected date of readiness, tenant names to be left in TRIAL mode vs. tenants that are approved for FINAL mode. The Product Management group must grant initial approval. Final approval must be granted by the Industry CloudSuite Executive Vice President.

If you feel you meet one of the above requirements, please create a support incident as indicated above and assign the incident to the group “White Glove”. You may also contact your Customer Service Representative for questions or assistance.

For further details on migrating from Ming.le to OS Portal, please reference Knowledge Base (KB) article 2277419

Hans Mueller

Hi Michael / all -

Regarding this call, here is the latest update I can provide. We had intended to have a call to discuss a potential solution to the Back button issue back in November. After further internal discussions, the call was cancelled because the proposed solution was not deemed to be in alignment with our future roadmap. That prompted the need to have further internal work on other potential solutions. I am told there is work now being done to address this issue, although as of today, I do not have details as to the timing and nature of how it will be resolved. I do know there is a commitment to deliver the solution in time for the April 2024 migration deadline.

I would strongly encourage all customers with these (and other concerns) to attend the upcoming Office Hours that will be held over the next two weeks. More information will be presented in those calls to hopefully allay migration concerns, and the product teams will be in attendance if there are further questions/challenges to be addressed to ensure customers are comfortable making the migration to OS Portal.

I am sorry there are not more details to provide at this time. Thanks for your patience.

Hans

Rebecca Derr

I just received this update to my ticket regarding the back button:

"Apologies for the delay in update. The Infor OS Development team reviewed the issue and evaluated some options. They recommended that the best option is to implement the solution within the specific application navigation.

Thus, we have coordinated this with GHR Team for better handling of this issue. They will continue to work on this and get back to you as soon as there is an update from their Development Team. We'll be closing this incident."

Same for me. I'm not sure what that means or why it is with GHR. It sounds like they will move forward with it as is though. I'm going to ask for some clarification.

Rebecca Derr

Sounds good. My thinking is that the back button would move back within each application (GHR, FSM, etc?). This would not address having the same application open in multiple tabs if so.

Ya, that would still be an issue.

i attended the teams call this morning and they had about 700 members attend with LOTS of good questions and about less than half were answered. One things not discussed was this back button issue but i posted the question in the official Q/A after the meeting was over in addition to my chat messages in hopes they will respond.

attending today and seeing all the questions made me realize there was more to check before this migration.

I don't think it is as high as the back button functioning oddly, but I could not find a distinguishing feature between our PRD and our TRN environment. Currently the image right next to the application switcher box will be a red PRD or a dark yellow TRN. Has anyone else seen this issue?

I should say outside of the web address

yes i have. i opened a ticket as recent as last week asking if there were global settings within the environments where i could color theme our TRN environment by default without allowing users to change themes so we could tell the immediate difference between environments and currently from what i understand is there is no global option to set that for all users by initial login. there are only a few color icons to choose from but i am looking for the whole theme to be different.

Where was this found?

I know this solution is not for everyone, but have you tried the right-click and duplicate of the browser tab itself? When I started testing it this morning I was running into the same issue where the back arrow would change tabs in the portal. I duplicated my tab and it's been working like how I'm used to working. I've only got a few hours working with it though, so not extensive testing.

Dr. Awesome

I see two interaction patterns here. I'm going to describe them and hopefully you can all validate my assumptions and understanding. First, let me be very careful with terms like "tab" and "workspace" as they are overloaded terms.

Two workspace types

1. widget based "start" workspace
2. application workspace

Two "tab" types

1. Portal tab
2. Browser tab

Three Portal tab types

1. widget based start workspace
2. application workspace
3. delivered application

Finaly, the two interaction patterns

1. a widget based start workspace (tab hws) driving into delivered application (tab hrt1)
User-expectation: browser back should take me back to widget based start workspace (tab hws) from the delivered application (tab hrt1) tab that it initially launched. My assumption here is that using browser back and crossing portal tabs here is good.

2. multiple duplicated application workspaces (tab hrt1, hrt2 and hrt3). these are created for MDI reasons and/or bookmarking.
User-expectation: intra-tab only, tab is "fenced", any back is contained only to the "current" portal tab. This is identical to browser tab behavior and browser back. I believe this is the "back issue" described in this thread.

How did I do?

you did great! yes number 2 is exactly what this thread is originally describing.

I haven't been able to figure out how to duplicate GHR Portal tabs (see image below) without duplicating the entire browser tab.

Also, I don't know if I clearly understand the difference between "application workspace" and "delivered application" in Three Portal tab types above.

ok i will admit i'm having trouble opening multiple GHR tabs. it will let me open different tabs to the different apps but opening multiple tabs for the same application i'm finding it hard to do so.

larrydaggett

Can you use "New Incognito window" in a certain browser to open multiple GHR tabs?

sorry but going back to the issue - if we have users who work within GHR and then CSF and use a workspace for widgets etc. working within each tab and using back buttons like we do for GHR today if we were to go into a work unit and then want to back out to get to the previous screen. if we were clicking in CSF or lawson or other tabs we have open then it was back out to those tabs even though we expect the back button to go back within the GHR tab we are in. does that make sense?

if you are in the workspace and click there to a shortcut that opens up my employee profile within GHR then yes hitting the back button takes you back to the workspace.

overall - the back button today takes you back for the tab you have open within chrome. the tabs opened within the infor OS portal - they do not function the same way as your chrome/edge/web browser tabs work.

Mychele Lee

I've had ER102775 open since Sept on this issue. You can duplicate workspace tabs but not application tabs (without several browser tabs). The ER has enough votes, but I'm not sure that development has looked at it yet.

Dr. Awesome

Yep, makes sense.

What is tricky here is that depending on where you are and how you got there the desire I'm seeing is that "back" should cross Portal tabs in some cases, while in other cases it should not. That user expectation and a consistent interaction design is currently conflicting.

At the moment Portal tabs were not designed or built to behave like browser tabs.

Btw, an "application workspace" is essentially a workspace you created that simply loads in an application of your choice. So you "Add a Workspace" and you'll see the options there.