You can use the Portal main page to configure the dashboard section instead of a separate section. This is the easiest option since most OOB sections cannot be added to Portal at all even with development.
In the screenshot I can not see the notification panel on Portal Workspace when portal user logs in. I want it to be visible to portal user in case of notification comes. Or else if there is another approach to notify portal user then please suggest.
Unfortunately, there is no OOB tools or information about partner customizations available which would add the notification panel for the portal user.
We will pass this request as an idea to the responsible R&D team so they will consider the possibility of adding the requested functionality in future Creatio releases.
I wanted the notification panel on Portal Workspace for process/requests he need to complete. The process has a pre-configured page. Which needs to be filled by Portal user. But process will only show in notification. Not in the Case I build on the section page.
Is there any other way to notify user to access and complete the process.
You can create "Web-page" dashboard that will display data and layout of some 3rd-party website where you can apply changes you need using HTML-code (create these blocks, adjust blocks layout, fill in those blocks with needed data and so on). And as a result all portal users will see a separate web-page in this dashboard (as an IFrame) and will be able to browse it and your business task will be achieved.
Unfortunately, there is no option to add the images to the dashboards. The solution might be adding the image to the dashboard section only using custom CSS styles. However, the custom CSS styles can be added only to a custom widgets, not lists.
Hi. I have read the articles about Portal Users that are available;
What portal users are. How to create them. How to set up their rights.
But what I want to know is what can't they do? Surely there must be some limits of a Portal User compared to a full licensed user.
Or is this just a result of what I allow my Portal users to do in my environment? Although I agree and understand that it would not be recommendable to let a Portal user do anything.
The application portal is a part of the platform used by external users and it is limited. There is no way to turn the portal user into the regular system user. The portal users' functionality is limited by the licenses and the objects permissions. Apart from that, there are a lot of back end functionality which is not compatible with the portal users. For example the portal users will not be able to run the database triggers for majority of the default functionality, access the portal through mobile application, run bulk emails, etc. Basically, there is no point to allow external users to use the application through the portal as a regular company employee. For this purpose, it is better to create a regular user for this individual. Theoretically it is possible to allow external users to use the application functionality on the company employee level, however it can only be done with the help of separate development project.
