Experience Cloud - Enable Flow Access - Possibly namespacing issue

Open
#94 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
cloud

Research direction

Compare the instructions screenshot with the actual Experience Cloud “Enable Flow Access” screen shown in the issue. First determine whether the additional namespace is expected behavior; done means confirming the expected screen or identifying the documentation or configuration that needs correction.

Written by the indexing model from the issue text.

Description

help wanted

The instructions screen shot looks like this:

Image

However, this is what it actually looks like:

Image

Note the additional namespace in the front. Is this a bug or expected?

Dominant language
Apex
Stars
9
Forks
22
Avg merge
2d 22h
Merged PRs (30d)
3

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SFDO-Community/UnsubscribeLink

All issues in SFDO-Community/UnsubscribeLink

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.