Idea Details

Internal usage of FQDN & display in Control

Last activity 20 hours ago
Walter Koller's profile image
By: Walter Koller
07-26-2022 08:22

It seems machines (runtime resources & workplaces) are always identified by their host names, regardless of system settings. 
In our case our settings were: 
register using short names, communicate using FQDN

However, the registration considered short names and FQDN and caused issues after DNS name change that made manual DB updates necessary.
The machines were verified based on their short names in BPAResource and Blue Prism crashed because of FQDN mismatch.

The only reason to chose 'register using short names' is to avoid long FQDN names in Control. Therefore:
1. add settings for short/FQDN in Control that is independent on communication and registration
2. always register and evaluate FQDN and never short names only


Ideas Portal

If you like this idea – vote! Ideas with over 20 votes will be highlighted to our Product review teams.
• Discussion is healthy! If you have a question or comment, don’t be afraid to jump in and start a discussion in the comments section below.
• Community collaboration is key!
New
This idea is new to the community and hasn’t been reviewed yet. While in the New stage, it is particularly important to vote and comment to further the discussion around this idea.
Duplicate
This idea already exists! A change to the Duplicate status will include a comment linking to the existing idea, so all voting and feedback can be collected in one place.
Need More Info
We’ve reviewed this idea, and determined we need a bit more info before deciding on how to move forward. An update to the Need More Info status will be accompanied by a comment explaining which additional details are needed. Ideas are still open for voting and comments while in the Need More Info stage.
Reviewed
We have all the info we need and are planning to review the idea for implementation feasibility and value added to the product. Ideas with this status are still open to community voting and discussion.
Under Consideration
We have all the info we need and are currently considering the feasibility of implementing this idea. Ideas in the Under Consideration status are still open to community voting and discussion.
Not Planned
We’ve reviewed this idea, and determined that it’s not feasible to implement right now. Ideas in the Not Planned status are no longer open for voting.
Planned
We’ve reviewed this idea and have determined that it will be delivered in the near future. Ideas in the Planned status are not attached to a binding timeline, but there is a concrete plan to implement this idea.
Planned-Now
We’ve reviewed this idea and have determined that it will be delivered for delivery in the next 6 months.
Delivered
Congrats! Your idea has been accepted by the team and is now delivered! Give yourself a pat on the back – you contributed to the improvement of one of Blue Prism’s products or services!