Replies posted by zach_davis
Inactive Dropdown values available in Report BuilderUnder Consideration
Hi All, I have added this to the backlog. Will increase the priority if more customers face this challenge. I think there are situations where you may still want to ignore the inactive values. We have a field, CS Engagement Model, that is used for our segmentation. We have changed from our prior values to a completely new set of values. We now see all of our old values in the drop down but have not credible use case for displaying them. I understand there are situations you may want to display them and would definitely want them to be distinguishable but there are valid scenarios where we absolutely do not want them to be visible.
@Anil Raj Pujari Is there any update on this? This does not sound like a feature, it sounds like a bug. If a default is configured on the drop down, would it not be considered a bug when that default is not applied when creating a record in a specific product area?
@waynedilworth Did you come up for a solution for this? We’re exploring using externally shared success plans but have the same concern as you. We would like to hide some objectives and also potentially have the users be able to edit the ones they own. This, to me, seems like one of the primary use cases of sharing a success plan.
Having the ability in the feature itself where one option to single click log to timeline (defaults to email type and the second option to modify the entry before logging (giving option to change type). Then end users can have both the quick option and the flexible options at their disposal. I came to say exactly this. I love the iteration here but I don’t feel it should be an either or situation. Providing an option to log directly to Timeline as well as an ‘edit’ option that surfaces the pop-up would be ideal for our users. FYI @darkknight
Oof - yes, @spencer_engel -- this is something that I came to understand, and understand why, it’s done this way -- even if the Gainsight user’s username is first generated from the connector to be the same as the SFDC username, it then becomes an independent, Gainsight username . . . since users can be enabled to log directly into Gainsight vs. logging in via SFDC NXT tab, we don’t want username, and username/password combos changing. It made sense to me once I pictured trying to convince a Salesforce admin that if I change a username in Gainsight, the SFDC Username should be automatically changed to match -- same request in the opposite direction -- and knowing what the SFDC Admin would think. THAT SAID, with so many Gainsight instance linked to an SFDC instance that is the only way the end users can log in, a utility, or checkbox, for a 1-time update when needed would help. I just know that architecturally, changing a username isn’t without downstream effects or lag time, etc. Fa
Remove Company Lookup on User objectUnder Consideration
@HollySimmons - With end user reporting you can remove access to company as an object for the SF licence holder group, in essence they would then only see User Object and not the lookup but the side effect would be they ( SF license holder group ) cannot report on company as a standalone object. ( is that acceptable ) @Azad not sure an all-or-nothing approach is going to be a very attractive proposition. If I have a report type I want users to have access to, but not have access to a lookup for whatever reason but the cost is that said users will no longer have the ability to report on that object anymore seems a bit too scorched earth for me and really takes away the utility of end-user reporting. FYI @darkknight and @zach_davis I agree with @bradleymcg here. Couldn’t this be handled with field level permissions?
Add Automated/Manual field to Customer StagesResponse from Customer
[url=https://community.gainsight.com/users/dan_ahrens]@dan_ahrens[/url] - I partially agree. Wouldn't you want to be able to handle all scenarios with a new feature? Manual, semi-automated and automated? From my experience it's fairly rare that a customer is able to automate ALL of their statuses. Yeah, we could just do CTAs to automate our manual statuses but why force the COMs to do more work just do drive 'full automation'?
Add Automated/Manual field to Customer StagesResponse from Customer
Good call out Jeff. I think ideally we would probably have to do some sort of mapping showng what stages can be set manually. Example: From stage 1 you can only select stage 2 and from stage 2 you can only select stages 1 or 3(if not automated stages).
[i]This reply was created from a merged topic originally titled [url=https://community.gainsight.com/gainsight/topics/clone-dataset-fetch-task-in-bionic-rules]Clone Dataset Fetch Task in Bionic Rules[/url].[/i] Do we have the functionality to clone Dataset tasks on the roadmap? I often have rules where I'm creating multiple dataset fetch tasks where the only difference is in the date filter. It would be nice to be able to clone these and change the dates rather than rebuilding 10+ tasks with only one field difference.
Dan - Most use cases for this are based on different levels of aggregation. They either require multiple fetches or a fetch and multiple transformations. Example: I want to aggregate data over the last month vs the prior 12 months. I could either select data and then do two transformations(which I would want to clone) or I could select data twice with two different sets of filters(which I would want to clone)
Include Group Score in Scorecard ExceptionsImplemented
[img]https://d1qy7qyune0vt1.cloudfront.net/gainsight-en/attachment/RackMultipart20180514-75009-1iw5ewh-unnamed-4_inline.png[/img] Essentially I want to be able to set the overall score based on one measure(Flagged Risk) and one group score(Customer Outcomes). We could possibly do this with a weight adjustment but I still think group scores in exceptions is a valid enhancement request for this use case(and possibly others).
I noticed that this no longer supports the MM/DD/YYYY format. for instance my dates are stored as 03/13/2018 and it is giving me an error unless I trim off the leading zeros. Is this a known issue? THis is a standard date format used by most US customers.
Email Assist Auto Populate RecipientNo Status
Nitisha, Yes, I am looking to be able to load in the user, just like we can currently load in a contact. I found that BCC functionality, but in this circumstance, they only want to BCC on this specific email assist task and not all of them. I was working on an outreach last night as well and realized we cannot tokenize anything from the user sending the email. Example: I am sending an outreach to the customer, I would like to be able to create user tokens in the email that will be populated by the user SENDING the email. For instance, we would like to build a signature based on fields from that user. Is this in the pipeline as well? Thanks!!
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at email@example.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.