Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
I
intranet-expenses
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
project-open
intranet-expenses
Commits
57625d51
Commit
57625d51
authored
Apr 04, 2017
by
Frank Bergmann
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
- Admins can always delete expense bundles
parent
9398efe6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
1 deletion
+7
-1
intranet-expenses-procs.tcl
tcl/intranet-expenses-procs.tcl
+7
-1
No files found.
tcl/intranet-expenses-procs.tcl
View file @
57625d51
...
...
@@ -236,8 +236,14 @@ ad_proc im_expense_bundle_new_page_wf_perm_delete_button {
}
{
Should we show the
"Delete"
button in the ExpenseBundleNewPage?
Only the owner himself is allowed to delete a bundle, while it
is in status
"Requrested"
or
"Rejected"
.
is in status
"Requested"
or
"Rejected"
.
Admins can do everything - as always.
}
{
# 2017-04-03: Admins need to delete bundles always, right?
set current_user_id
[
auth::require_login
]
set user_admin_p
[
im_is_user_site_wide_or_intranet_admin
$current
_user_id
]
if
{
$user
_admin_p
}
{
return 1
}
set perm_table
[
im_expense_bundle_new_page_wf_perm_table
]
set perm_set
[
im_workflow_object_permissions -object_id
$bundle
_id -perm_table
$perm
_table
]
return
[
expr
{[
lsearch
$perm
_set
"d"
]
> -1
}]
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment