Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*{!ComponentName}* - _({!ElementName})_ - {!BugTitle} #1510

Open
kurtfairfield opened this issue Jan 16, 2024 · 2 comments
Open

*{!ComponentName}* - _({!ElementName})_ - {!BugTitle} #1510

kurtfairfield opened this issue Jan 16, 2024 · 2 comments

Comments

@kurtfairfield
Copy link
Contributor

Steps to reproduce

Steps to reproduce the behavior:

  1. Install Screen Flow Base Pack
  2. Create Experience Site configured with Public Access
  3. Create Screen Flow and add to Experience Site
  4. Site displays error "Hmm, that didn't work. Check your internet connection and try again, or refresh the page. If the problem continues, ask your Salesforce admin to contact Salesforce Customer Support."
  5. Try to add SUF Screen Pack Permission Set to Guest User for the Experience Site
  6. Get error 'Can't assign permission set USF Flow Screen Components to User ****. The user license doesn't allow permission Edit FlowTableViewDefinition__c

Expected behaviour

Should be able to use Screen Components on Guest visible Flow

Actual behaviour

Screen Flow is blocked from loading, even when removing the Screen Components. Did not resolve even after uninstalling packages. Attempting to workaround via a new Sandbox to see if the issue is related to the installation and modification of permissions required for screen flows with respect to guest users.

Screenshots

image

@alexed1
Copy link
Owner

alexed1 commented Jan 24, 2024

@ericrsmith35 any ideas on this?

@ericrsmith35
Copy link
Collaborator

ericrsmith35 commented Jan 24, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants