7 results found

1. Make the Salesforce Marketing Cloud (ExactTarget plugin work for multiple Business Units

   Problem
   We are using the Plugin in Optimizely CMS to easily connect Optimizely Forms to Salesforce Marketing Cloud Data Extensions. This works very well when the user that's used to configure the connector only has access to 1 Business Unit (MID in Salesforce. However, as I understand from Salesforce, many customers work with instances that have multiple Business Units. This means that from Salesforce stand point, you need to provide to which Business Unit you want to connect when authenticating, but the plugin does not provide a means to specify this. To solve this, we now had to create multiple users in Salesforce, each only able to connect to one of their Business Units. This increases the costs of the implementation, because each user is an additional license.
   Suggested solution
   When authenticating a user using the API in Salesforce, you can provide an accountid to specify to which Business Unit you want to connect within the instance. Information about this can be found here (https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/access-token-s2s.html .
   Add an optional field to the default set of fields when configuring a connector, where an MID can be specified. Use that value for accountid when authenticating to Salesforce.
   This way, whenever a user has access to multiple Business Units (MIDs, the same user can be used for different connectors, connecting to any available Data Extension.

   Problem
   We are using the Plugin in Optimizely CMS to easily connect Optimizely Forms to Salesforce Marketing Cloud Data Extensions. This works very well when the user that's used to configure the connector only has access to 1 Business Unit (MID in Salesforce. However, as I understand from Salesforce, many customers work with instances that have multiple Business Units. This means that from Salesforce stand point, you need to provide to which Business Unit you want to connect when authenticating, but the plugin does not provide a means to specify this. To solve this, we now had to create multiple… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Enable selection of datetime format on DateTime block in EPiServer.Forms

   The current implementation of the DateTime element (found in the EpiServer.Forms.Samples package appears to be insufficient.
   In the DateTimeElementBlock.js file, the logic used to determine the language format relies on the browser's language settings. However, this approach fails, as many Danish users have their browsers set to English (US by default, resulting in the language code en-US. This causes the jQuery date picker to display the wrong date format.
   var _utilsSvc = epi.EPiServer.Forms.Utils,
   language = navigator.language || navigator.userLanguage, // on iOS naviagtor.language is in lower case (ex: en-us
   dateFormatSettings = epi.EPiServer.Forms.Samples.DateFormats[language.toLowerCase(] || epi.EPiServer.Forms.Samples.DateFormats["en-us"],
   dateFormat = dateFormatSettings.pickerFormat;
   A better solution would be to allow users to select the language format directly within the block itself. This would be a more modular and user-friendly approach, in line with best practices for Optimizely implementations.

   The current implementation of the DateTime element (found in the EpiServer.Forms.Samples package appears to be insufficient.
   In the DateTimeElementBlock.js file, the logic used to determine the language format relies on the browser's language settings. However, this approach fails, as many Danish users have their browsers set to English (US by default, resulting in the language code en-US. This causes the jQuery date picker to display the wrong date format.
   var _utilsSvc = epi.EPiServer.Forms.Utils,
   language = navigator.language || navigator.userLanguage, // on iOS naviagtor.language is in lower case (ex: en-us
   dateFormatSettings = epi.EPiServer.Forms.Samples.DateFormats[language.toLowerCase(] || epi.EPiServer.Forms.Samples.DateFormats["en-us"],
   dateFormat = dateFormatSettings.pickerFormat;
   A better solution would… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. No error display when form submit not successful

   We want to use Marketing automative Salesforce connector for Optimizely CMS(Customer Management System form to connect with our Salesforce platform.
   But we find out there are no submission failure show up on CMS interface, only recording the submit data in "form submission" dropdown.
   This is unhelpful and not user-friendly for CMS user, developers, and infrastructure people. We cannot track/ debug/ get notice when form is submitting unsuccessful when Salesforce end shows data field mapping error.
   There's no way every-time we have to login application insights, and search for request unsuccessful/ view live log stream. Please add the error notice, error message in form submission; The form submission only records what data website audience input, but it doesn't show are those data fields are really POST to Salesforce or not... This is not make sense....
   This is a Nuget package in half-way finish, i can see in Marketing automative Salesforce connector code it do have error handling but no further steps to show the message in CMS interface.
   And to give your team some example of what we are looking for showing up I also attached a form submission plugin i built myself. This is real-time track and can see payload, error message.

   We want to use Marketing automative Salesforce connector for Optimizely CMS(Customer Management System form to connect with our Salesforce platform.
   But we find out there are no submission failure show up on CMS interface, only recording the submit data in "form submission" dropdown.
   This is unhelpful and not user-friendly for CMS user, developers, and infrastructure people. We cannot track/ debug/ get notice when form is submitting unsuccessful when Salesforce end shows data field mapping error.
   There's no way every-time we have to login application insights, and search for request unsuccessful/ view live log stream. Please add the error notice, error… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. [Feature request] Display forms in 'For This Site' and 'For This Page' sections when creating an EpiServer Forms criteria under Audiences

   Dear Team,
   Currently, when setting up EpiServer Forms criteria in Audiences, we can only select forms listed under the 'For All Sites' section. However, our business also requires the use of forms from the 'For This Site' and 'For This Page' sections.
   It would be helpful if future releases could include this feature.
   Thanks!
   Best regards,
   Lisa

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. EPiServer.Forms.Samples uses out of data JQuery.UI with known vulnerabilities

   One of our customers is using the EPiServer.Forms.Samples library, mostly to facilitate content gating with the Forms Visitor Groups. During a recent penetration test the following was reported:
   We also observed the use of a known vulnerable version of jquery-ui at /Util/EPiServer.Forms.Samples/jquery-ui/jquery-ui.js which is known to have the following vulnerabilities
   CVE-2022-31160 (https://nvd.nist.gov/vuln/detail/CVE-2022-31160 : XSS when refreshing a checkboxradio with an HTML-like initial text label
   Recommendation
   Use the latest versions of the dependencies where possible. If it is not possible to update these, ensure the vulnerable components are not used.
   There does not appear to be an equivalent of the forms.config that would allow us to prevent the injection of jquery-ui.js for the EPiServer.Forms.Samples package.
   Can we please get an update for this package so that the out of date library is not used, and if possible, the capability to disable this from needing to be injected.

   One of our customers is using the EPiServer.Forms.Samples library, mostly to facilitate content gating with the Forms Visitor Groups. During a recent penetration test the following was reported:
   We also observed the use of a known vulnerable version of jquery-ui at /Util/EPiServer.Forms.Samples/jquery-ui/jquery-ui.js which is known to have the following vulnerabilities
   CVE-2022-31160 (https://nvd.nist.gov/vuln/detail/CVE-2022-31160 : XSS when refreshing a checkboxradio with an HTML-like initial text label
   Recommendation
   Use the latest versions of the dependencies where possible. If it is not possible to update these, ensure the vulnerable components are not used.
   There does not appear to be an equivalent of the… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Missing autocomplete-attribute in Forms module

   In the Forms module we are missing the possibility of setting the autocomplete-attribute, and therefore WCAG 1.3.5 is broken. Will this be fixed in a future update of Forms?

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Language translation of email contents in Episerver Forms

   As a an editor I would like to translate the contents regarding "Send email after form submission" on the "Settings" tab in order to send e-mails with the correct language to end users, especially with regards to subject and message. This is not currently possible since this list-property is not culture specific.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Forms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating