Tasks
Tasks, projects and team collaboration.
12 pages
All topics in this area
- Asana ImportThis page controls migrating data from your previous Asana account into SELLERLOGIC Commerce Services. You connect Asana via a personal access…
- Asana MatchesDuring Asana Import, projects and tasks are initially brought in without a fixed customer link. On this page you review suggestions for which customer…
- Automation Rules (Tasks)Automation rules handle recurring housekeeping in a project automatically: when a specific event happens (e.g. a task is completed), SELLERLOGIC…
- GoalsGoals let you track measurable metrics (similar to OKRs — "Objectives & Key Results," i.e. goals with measurable key results) over a set time period, and…
- InboxThe Inbox is your notification mailbox for tasks you follow. Here you see when a task is assigned to you, someone mentions you, a comment is added, or…
- My TasksThis page brings together all tasks assigned to you from every project in one place — organized into your own, freely arranged sections. It's your…
- PortfoliosA portfolio groups several projects together so you can track their status at a glance — for example, all projects belonging to a specific campaign or…
- Projects (Project Management)This module is a standalone project-management tool with budget, milestones, a Kanban board, time tracking, and team resource planning — separate…
- Task TypesTask types let you define your own templates for recurring workflows — such as "Call", "Complaint", or "Approval" — including custom fields, an individual…
- Task WebhooksTask webhooks automatically notify external systems when something changes in SCS Tasks — for example, when a task is created or completed. This…
- Tasks — HomeThe Tasks Home page is your personal entry point into SCS Tasks — the built-in replacement for Asana. It shows at a glance what's due today, what's…
- Tasks Overview"Tasks" is the central module for project and task management in SELLERLOGIC Commerce Services — the built-in replacement for Asana. Here you…
What's new?
-
Project list now shows a fault message instead of sample data on a load error (#3406)
A failed project list request used to silently show five fixed sample projects as if the request had succeeded - an outage was indistinguishable from real project data. The list now shows a visible notice that loading failed.
Open the Knowledge Base → -
Task webhook subscriptions now record who created them (#3228)
Creating a webhook subscription for task events worked, but silently left the "created by" field empty, so nobody could tell later who set it up. It now records the acting admin.
-
Dropdowns in tasks and projects are now read out by name (#2859)
Affected were the task list with project, priority and assignee, goals, custom fields, task rules with trigger and action, webhooks, templates with section and priority, team management and project sharing with role and team, the Asana import, and in the project area the project list with status, priority and sort order, the kanban board, the task list and time tracking. All of them now carry a spoken name in German and English. Nothing changes visually. Tasks · Rules ·
Open the Knowledge Base → -
"Redeliver" in the delivery log now asks first - and names the target address
Redelivering from a webhook's delivery log used to fire on the first click. It is not a local retry: the payload goes to the address you configured, carrying a valid signature, and is indistinguishable there from the original delivery - depending on the receiving system it can trigger an order, re-open a case, or create a record twice. Nothing on this screen can recall it. A confirmation now appears before it is sent, naming the event and the target address the signed delivery goes to. Only confirming sends it; cancelling sends nothing. The delivery itself, the retries and the log are unchanged.
-
SCS now creates tasks by itself - and closes them by itself too
when an employee submits an absence request, a real task is now raised for their direct supervisor - with title, period, a link to the decision, and a due date three days after submission. It therefore sits in My Tasks alongside everything else that has to be done, instead of living only in the bell. The important part is the closing: as soon as the request is approved, rejected or cancelled the task is complete - including when somebody else decided it, and without anyone having to tick it off. Where several people are responsible, each has their own task and all of them close together the moment one of them decides. A task cancelled by hand stays cancelled - it is not quietly flipped to "completed" later. The request is still decided under HR → Absences → Requests; the task takes you there but does not replace the decision.
Open the Knowledge Base →