Skip to main content
Solved

EDM Repository - Wildcard Document Class in Cloud

  • November 2, 2022
  • 2 replies
  • 99 views

durette
Superhero (Customer)
Forum|alt.badge.img+19
  • Superhero (Customer)
  • 542 replies

Under EDM Repositories in Apps 9, we use a wildcard * for the Document Class.

This wildcard isn’t honored when I uplift this setup into Cloud, nor can I save a repository in Aurena if it has this wildcard.

We have nearly a hundred document classes but exactly one document repository. Is there a way to avoid duplicating the EDM Repositories setup across all our document classes?

Best answer by Mathias Dahl

It should still be honored, but we had a bug where you could not create such a record, which is fixed now (not sure on which track though).

Are you sure the wildcard is not honored if the status is Generating? That's a big that should be reported, if it is the case.

2 replies

Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Superhero (Employee)
  • 2903 replies
  • Answer
  • November 2, 2022

It should still be honored, but we had a bug where you could not create such a record, which is fixed now (not sure on which track though).

Are you sure the wildcard is not honored if the status is Generating? That's a big that should be reported, if it is the case.


durette
Superhero (Customer)
Forum|alt.badge.img+19
  • Author
  • Superhero (Customer)
  • 542 replies
  • November 3, 2022

Are you sure the wildcard is not honored if the status is Generating? That's a big that should be reported, if it is the case.

Yes.

Thank you.