I'm trying to add a unclaim/claim task button on a custom page.
I'have add the TaskListModule on the imports of my module.ts.
and when i add the "<button adf-unclaim-task [taskId]="taskId" (success)="onUnclaimTask()">Unclaim</button>" i got that error :
Uncaught Error: Template parse errors:
Can't bind to 'taskId' since it isn't a known property of 'button'.
do you know how to correct this error ?
we're trying to use the
adf-unclaim-task directives, that takes
taskId as a required property
we're following ADF Doc : https://www.alfresco.com/abn/adf/docs/process-services/directives/unclaim-task.directive/
the directives seems to be in the "TaskListModule"
we added it in our module, but we still have the error mentioned above
@DenysVuika We are testing the withCredentials changes with Kerberos, looks like the authentication works fine. I do observe that the top right user icon and user info on the toolbar is not getting displayed. Is this something known issue and will be addressed?
Hi, I'm facing the same problem but on ADF 3.7.0 (old project, I know). I removed the login component, set the right conf in the app.config.json file and remove canActivate[AuthGuardEcm] in routes. I can go into my app but can't see the User Info and other things doesn't work as usual. My problem is on ADF not ACA but it looks like the same. Thanks.
npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: email@example.com npm ERR! Found: @firstname.lastname@example.org npm ERR! node_modules/@angular/compiler npm ERR! @angular/compiler@"10.0.6" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer @angular/compiler@"^6.0.0 || ^7.0.0 || ^7.2.0-beta.0" from email@example.com npm ERR! node_modules/ng-packagr npm ERR! peer ng-packagr@"^2.2.0 || ^3.0.0 || ^4.0.0" from @firstname.lastname@example.org npm ERR! node_modules/@angular-devkit/build-ng-packagr npm ERR! dev @angular-devkit/build-ng-packagr@"~0.10.0" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/luis/.npm/eresolve-report.txt for a full report.
if something is not working, I suggest just raising a GitHub issue directly, with steps to reproduce
Thanks, Denys. It's a reproduceable issue, so I created this issue: Alfresco/alfresco-ng2-components#6912