There are no basic tools to add the timeline tab through the section wizard. The same relates to the portal case page. You will need to involve the development process to add the timeline tab to any page in the system but as for portal, there is no much reason to add it since this detail has multiple connections to other entities in the system. Apart from that, the portal users might not have the access rights those entities.
Could you please let us know what is your business task?
Thank you Dean. If it requires custom development, I don't think we would want to implement. We were just checking to see if there was a standard and simple solution.
We enjoy the timeline tab for internal cases, we like how you can filter by date and by type of activity on the timeline. We thought it would be beneficial for our portal users to have this function if it was an option so they could put time filters on the entities that they have access to.
Thanks for your response, my question has been answered.
It`s not possible to create system users via OData because system user is not only one record in SysAdminUnit table, actually, when system creates new user, many other connections with main record are created through other tables.
Basically, the best way to create a new user is to emulate the way the system does it. In order to do so you need to catch queries, which system creates when adding a new user and replicate same queries from your external application.
I have another web service link which required output is in XML format. I'm not sure if its configurable in Process library or it will be only possible through code customization.
Below is screenshot of specific area of output from that web service link
Can you control access for users to which lookups they can view and edit? I see there is an operation permission called Access to "Lookups" section. But what if I want the user to only be able to edit one lookup? Can I control that? or is it an "all or none" type of setting?
As for now there is no such functionality to set up access rights for certain lookup only. I have forwarded your request to our business analysts. They will evaluate the possibility of implementation in future system releases.Thank you for helping us to make our application better!
I would have to give her access to the lookups, but she would be getting access to way too many objects.
This is one specific case but there are many others were we have an intermediate level user that is not administrator but that should be the owner of 1 or 2 specific lookups, I believe this is much needed.
we had a similar request from our client, we handled it by creating a new workplace and added only lookup section. and gave access to specific user role.
I have created an entity similar to "Case", and I want to add to it an auto-genetared code number, similar to the "number" . Is this posible? Can I add an autogenerated number to an entity?
Hello, does the [Activities] Section only display tasks in the list view? Is it not possible to display email type activities? I can view emails in the activities lookup, but there are no records returned if I filter on type = Email in the activities section list view.
Your observation is correct. The activities section does not show the emails by default, since your real activities can be lost in the correspondence. You can view your emails in the CTI panel, or you can create a lookup for the activities of the email type.
When a user clicks on the case feedback icons, they get taken to a web page that just shows a thank you image. Yet the documentation and the case field has a Text feedback field included. How can I get that feedback text input enabled, so written feedback can also be provided?
Is there a reasonable means of automating the adding of contacts as portal users?
Possible scenario, a lead is created from a landing page from which a bpm'online Contact is created. A Lead case then guides to a step where a portal user is to be created from this Lead Contact.
Can a step within a case accomplish this function either through configuration or light customization?
It is possible to achieve the described behavior in a couple of ways depending on your vision of the task.
In case you want a user to register automatically, you can create a send email dcm element, that will send an email to a contact asking them to register on a portal. In this email you can send them a link to the portal self registration page.
In case you want to create a user automatically, you can create a business process, that would be triggered once the record reaches the desired stage. Then, this process can create a portal user for you. Please note, that you will also have to distribute a license to a new portal user, either with the help of a process or manually.
We implemented a Landing page to create Case (Web-to-Case) in which we have Email, Name and Phone Number of the Contact.
When the Contact doesn´t exist in the environment it is properly being created (which is right). However, if the Contact already exist, the newly created Case is assigned to the existed contact (which is right) but the phone number is not getting updated even if it is originally null.
You can create your custom Process started when Contact is assigned to Case. In this process you can compare received Communication options with existing ones and add them if necessary
The logic for creating cases from landing pages is covering setting of mobile phone when initially creating a contact for case. The logic is as follows:
If contact fields matches the [Name], [Email] and [Phone] fields from the filled form, they will be added to the created case.
If contact fields matches only the [Name] and [Email] fields from the filled form, they will be added to the created case.
If contact fields matches only the [Email] field from the filled form, it will be added to the created case.
Otherwise, a new contact is created and the [Name], [Email] and [Phone] fields will be filled in. The created contact is added to the registered case.
In case you indicate the existing contact, the mobile phone value will be ignored and won't update the existing contact with the values from landing.
Concerning to the following sentence: "In case you indicate the existing contact, the mobile phone value will be ignored and won't update the existing contact with the values from landing."
We are looking for a way to change this behavior and actually update the existing contact (on steps #2 and #3 of the logic you described). Is this something we can do?
If not, is there a way to remove the Phone from the Web-To-Case landing page without causing this to break the form submition?
There are two ways of achieving your task. The first one requires much of advanced development. You can override the
WebFormCasePreProcessHandler source code so it will be processing the web-to-case logic in the way you need it.
The second one is to create a field, e.g, mobile phone in the Case object. In the config on the landing page you map the mobile phone input to both mobile phone in Contact object and Case. Create a business process, which would be triggered when contact is linked to the new case. Check whether contact has a mobile phone, and set the phone if it exists in the custom phone column of Case object.
Therefore, when case with existing contact and firstly indicated phone will come from landing, the existing contact will be linked to the case, just inserted phone will be added to case phone column and business process will set it to the contact.
This is probably not the most elegant way, but the one I can think of.
