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

[Feat] Find target Procedure via original filename pattern #99

Open
simonhir opened this issue Feb 7, 2025 · 1 comment
Open

[Feat] Find target Procedure via original filename pattern #99

simonhir opened this issue Feb 7, 2025 · 1 comment

Comments

@simonhir
Copy link
Member

simonhir commented Feb 7, 2025

Use case: Procedure COO not in filename as not known as filename was defined

  • Extract Procedure name from original filename
  • Parent File also not known but COO of other parent higher in the hierarchy
  • Search under parent for Procedure with extracted name
    • Procedure with name needs to exist
  • Create new Incoming in found Procedure

Questions

  • Is it possible to search under a certain object an how? SearchObjNameGI/SearchProcedureGI
@simonhir simonhir mentioned this issue Feb 7, 2025
11 tasks
@simonhir simonhir changed the title Find target Procedure via original filename pattern (Optional) [Feat] Find target Procedure via original filename pattern Feb 7, 2025
@simonhir
Copy link
Member Author

simonhir commented Feb 7, 2025

Original comment from @rowe42 in #21

regarding

Find existing target Procedure via original filename pattern

Reply from dms-team regarding the question above:

SearchObjQueryGI wurde nicht umgesetzt dort hätte man eine Suchquery hinterlegen können.
SearchObjNameGI hat die Möglichkeit nach einem Teilstring bei sämtlichen Objekten zu suchen.
Eine Einschänkung auf Aktenplan oder wohl eher Akteplaneintrag oder Akte ist bisher nicht möglich.
SearchProcedureGI lässt leider keine Teilstrings zu, dort kann man jedoch auf Akte einschränken.

So, none of the above is really a good option. So, if realizing this usecase, we would need to use SearchObjNameGI, hence not further restrict the search in a certain area ("Aktenplan/Aktenplaneintrag") in the dms. That means that the name needs to be unique throughout all reachable objects. And the question is how much a global search will affect performance.

Before we further implement this, I will check whether a search with SearchObjNameGI but with restricted view rights could be an option.

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

No branches or pull requests

1 participant