Is there a way to display the print button and allow portal user to download reports including fastreports. I tried giving access to specific objects and adding them in "List of objects available for portal users" lookup. After adding this configuration the print button is shown but I cannot download fast reports due to access rights and the following message is shown "Failed-Forbidden".
This message is only shown for fast reports printables. Word printables are downloaded successfully. Is there something that I'm missing in the configuration?
If the available information is sufficient for further work on the lead, qualify the lead without opening the record page. To do this, select the record in the list and click [ Qualify ].
The following instructions can help you to achieve the result you are looking for:
If the available information is sufficient for further work on the lead, qualify the lead without opening the record page. To do this, select the record in the list and click [ Qualify ].
The following instructions can help you to achieve the result you are looking for:
Add the following code in the page schema of main object under methods:
isDetailEnabled: function(detailName){
var DCMStage =this.get("UsrDCMLookup").displayValue;if(detailName ==="ExampleDetail"){if(DCMStage ==="Approved"){returnfalse;//Disable the "+" button}else{returntrue;//Enable the "+" button}}returnthis.callParent(arguments);}
using Terrasoft.Web.Common;using Terrasoft.Web.Common.ServiceRouting;[ServiceContract][DefaultServiceRoute][SspServiceRoute][AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Required)]publicclass Service1 : BaseService
{//Code}
For system users the service works fine but when I try to access the service from postman authenticated as a portal user I get the following message : "IS 10.0 Detailed Error - 403.0 - Access to non-SSP API is denied for portal users" with 403 status code. Is something that I am missing in the service implementation or in web.config?
I am using perform task inside section cases. The task updates the entity stage. After the stage is updated from the task I want to catch this event and reload the entity from the client side. I tried using the following approach but nothing happens
The below script is called only when the stage is updated directly from the client side and not from a task or a business process. Is there a way to catch this event from the client side?
Since the automatic changing of a stage happens outside of the context of a page, you won't receive any events from the change on the page itself.
The only option is to either use a process, entity subprocess or entity event listener class (and starts with a signal of case modified in stage field) and if it's changed to the appropriate stage you send a signal to the client. You can see how to send a message from the server (such as from a process) to the client here: https://customerfx.com/article/sending-a-message-from-server-side-c-to-…
You'll add code to the page to listen for this message and then reloadEntity to refresh the page.
Since the automatic changing of a stage happens outside of the context of a page, you won't receive any events from the change on the page itself.
The only option is to either use a process, entity subprocess or entity event listener class (and starts with a signal of case modified in stage field) and if it's changed to the appropriate stage you send a signal to the client. You can see how to send a message from the server (such as from a process) to the client here: https://customerfx.com/article/sending-a-message-from-server-side-c-to-…
You'll add code to the page to listen for this message and then reloadEntity to refresh the page.
I am trying to connect a full organizational role with an organization. To implement this solution I want to update the Account column of SysAdminUnit table which is impossible from the client side. Is there a way I can update the Account column of SysAdminUnit?
Could you please specify what is the purpose of connecting an organizational role with an Account? Organizational roles are used to distribute access rights between the users in the system, however, organizations and accounts do not have access to the system.
Such logic was implemented only for portal users since the Self-service Portal was designed only for them and they could be from different companies (from the accounts section).
Such logic was implemented only for portal users since the Self-service Portal was designed only for them and they could be from different companies (from the accounts section).
