Is it possible to deploy to live just one app’s page instead all the application?
Thanks
Why not? 
Could you tell me how?
I misinterpreted the question.
Answer is … nope
A big limitation unfortunately
I’m not sure why is the advantage to publish only one page, but you can rename all other pages with impossible name to reach? Be sure the option of Swagger is Hide.
1 Like
It would be useful because I happen to work on two pages at the same time and while one page I have completed, I am still solving problems on the other.
I want that the user could reach the other pages
You can create a dashboard with all checkbox for every page accessible for you user or not, and let them know “Page will be available soon”.
I don’t think that Hiding swagger api documentation is usefull in this case
It was for security purpose. Great it doesn’t apply to your case.
Study how an Airdev’s Canvas Bubble template deals with page / userRole redirection logic. You may want to implement a subset of how their mechanism works.
1 Like
No it’s very simple my problem:
I have 2 pages:
1 is ready to be update
2 not
I want to publish hust the n.1, and the user could use the “older” version of page 2
1 Like
I see. That’s why we have DEV and LIVE, no? You can still rename your second page with the name of your first one and publish it. But your are doubling the process unless is 2 different pages.
1 Like
Elaborate way to deal with this (partial page/userRole redirection structure):
-
1st options set called “appPageOS” where the display is the exact name of the page.
-
2nd options set called “userRoleOS”
-
add an attribute to “appPageOS” called “thisPageAllowedUserRoles” that is a list of “userRolesOSs”
-
add the “userRoleOS” to the userObject (… the user dataType)
-
manually add options for all of your app pages in “appPagesOS” … make sure that you name each option’s display exactly as each page is named
-
manually add each allowed OS user role to each of the OS pages … (example: page1, page2, page3 | userRole1-appAdmin, userRole2-standardUser : page1-adminPortal has only the appAdmin user allowed, page2-ReadyToPublishPage has the stdUser allowed, page3-WorkInProgressNotYetReadyToPublishPage has NO users in the allowed list of userRoles)
-
your app must have a header reusable … if not … consider placing your header in a reusable element so that you can use it on every page in your app
-
add logic in the header that only allows the page to load if the current user’s role is in the appPageOS whose display is equal to the current page’s name. else send them to your index page or wherever else in the app that an unauthorized userRole should go
… hope the above makes sense
2 Likes
No it’s very simple my problem:
I have 2 pages:
1 is ready to be update
2 not
I want to publish hust the n.1, and the user could use the “older” version of page 2
You can always try this…
Rename the page you’re working on which isn’t finished… and set it up so it can’t be viewed by anyone without admin rights… (also make sure it can’t be found or indexed by search engines)…
Go into the ‘Live’ version of your app editor and copy the live version of the page, then go back and paste it into the ‘dev’ version of your app… make sure to change any ‘Go To Page’ actions, or ‘internal page links’ to the ‘old’ version of the page…
You now have the original, unchanged, page in your dev version, along with a copy of that page which you’ve updated, but is not yet finished. So when you deploy, the original version of the page will remain unchanged, and the updated version will not be viewable by the public…
Then, when you’ve finished updating the page, simply delete the original, and rename the new version back with the same name as the original… then deploy… you might have to fix any broken ‘Go to page’ actions in any workflows, or ‘internal links’ that point to the page (although anything referring directly to the URL should be unaffected) .
2 Likes
This topic was automatically closed after 70 days. New replies are no longer allowed.