Skip to content
  • 15 Themen
    15 Beiträge
    thuthT
    The Location Autocomplete allows the user to automatically determine the location based on a previously created user-defined database after entering a postal code. Once the module is started, it creates a user-defined database (@CMP_ZIPCODES). In this database, the user can manually enter locations, postal codes, and the country code (ISO 3166 ALPHA-2). The database can be accessed via: [image: 1718866378964-f29c2efe-5331-4911-a82e-04b507fea1b1-image.png]
  • 4 Themen
    4 Beiträge
    thuthT
    An area for official communications about updates, patches, and new features.
  • 4 Themen
    4 Beiträge
    thuthT
    An area for official communications about updates, patches, and new features.
  • 7 Themen
    23 Beiträge
    thuthT
    COBI.time - User manual for the Manager Purpose and area of application The following is a supplement to the user manual for the standard user of COBI.time for employees in management positions with employee responsibility. It supports the user in maintaining an overview of employees' time accounts and absences and in processing absence requests directly in COBI.time. The modules for the supervisor/manager function are activated by the administrator via the user rights administration. This manual covers the following additional modules: (Administration) - see Administrator user manual * Attendance list * Time report * Absence overview The Administration module is not covered in this user manual; please refer to the manual for the administrator. After logging in to COBI.time, the supervisor receives the same dashboard as the standard user, but with the additional modules in the left menu bar, outlined in yellow in the image below. [image: 1716551282604-85._dashboard_manager.jpg] 1. Attendance List [image: 1716551406244-86._presence_list.jpg] Please refer to the user manual for the standard user for the general functions. The supervisor/manager can view the following information about the employees. Clicking once on an employee opens an overview window in which you can find an overview of the current working time, the time account balance and the holiday days, see illustration below. [image: 1716551418998-87._presence_list_2_.jpg] In addition, the supervisor has the option of clicking on the “Balance” to display the employee's monthly history. [image: 1716551428920-88._monthly_history.jpg] The following window opens. A monthly overview is displayed showing the times and absences already booked. You can scroll forwards and backwards month by month using the arrows to the left and right of the monthly display. [image: 1716551438298-89._monthly_history_details.jpg] By clicking on a single day, you get an overview of the time recording per day. [image: 1716551458710-90._history_single_day.jpg] If the employee has requested a time correction or for any other reason, the supervisor can correct times manually in this view and add a comment to the correction. The comment field is only mandatory if it has been activated in the general settings. Link zu den Einstellungen The comment may not exceed 400 characters. Options for time correction: [image: 1716551465216-91._edit_history.jpg] If you click on a time that has already been booked, you can now set a different time. Clicking on the arrow next to the status opens a selection menu in which a status can be selected accordingly. You can add lines via the “plus” if, for example, you would like to add times to a project. The entry does not necessarily have to be entered in the correct order of the daily schedule. The line automatically jumps to the correct position when the “Enter” key is pressed after the correction. If the comment field is activated, it must also be filled in, for example the reason for the time correction can be entered here. Otherwise, you cannot save the changes. You can use the “Show comments” function at the top right to display the corresponding comments for the changes. When you click on the button, only days are displayed for selection where changes have been made; after selecting the day, for example, the following overview is displayed: [image: 1716551476138-92._show_comments.jpg] The supervisor also has the option of having a time report created from the employee. For this purpose, click on the icon ( highlighted in yellow) next to the balance in the information window. [image: 1716551483438-93._information_field_time_report.jpg] The “Time report” is a separate module in the menu bar, which can be applied to all employees (see point 3.) and can also be called up within the information window of the individual employee, exclusively for this employee, after clicking on the employee within the attendance list. The general view and the structure of the time report are the same. After requesting the employee's time report, you get the following view (example of a week in Feb.24): [image: 1716551491223-94._time_report.jpg] The actual and target working time, the difference in per cent and the corresponding balance are displayed. The booked times including the break are visible for the individual days. If projects have been booked, you can see these by moving the mouse pointer over the project symbol. The red arrows to the left and right of the name can be used to scroll forwards and backwards by month. This information can be imported into Excel via the “Export” button and processed accordingly. 2. Absence Overview [image: 1716551505785-95._absence_overview.jpg] The “Absence overview” module in the menu bar gives the manager an overview of the remaining holidays, already booked and requested absences of the employees. Clicking on the icon opens the following screen. [image: 1716551511578-96._filter_absence_overview.jpg] You also have the option of filtering by teams or individual employees or clicking on “All employees” to get a complete overview. If you have selected a team, the “Employees” filter only displays the employees of this team and you then have to select them either completely or individually. You can also use the date or month selection to display absences in the past. Below is an example of the view of an absence overview: [image: 1716551517598-97._absence_overview.jpg] If nothing else is selected, the current month is always displayed in the absence overview; you can scroll forwards and backwards using the arrows to the right and left of the date. The search function at the top left takes you back to the filter mask. If you move the mouse pointer over the “Remaining holiday” field, you will see an overview of how this is made up, as shown above. The exclamation mark next to the employee's name indicates that the employee has submitted an absence request. Requested and unconfirmed absences are marked with an asterisk in the calendar. In the top right-hand corner, it is possible to display the name and colour legend of the reasons for absence. ADDITION: The manager can also find the notifications of absence requests in the dashboard under “Notifications”, these can also be edited from there, see illustration below and picture at the top of the dashboard, point 4. [image: 1716551528792-98._notifications.jpg] Approval/rejection of absences There are two ways to approve absence requests. Firstly, you can click on the exclamation mark icon and all of the employee's absence requests will be listed one below the other. Based on the information “Received on:” under the reason for absence, you can decide which absences should be approved. This would also be a helpful decision-making aid, for example, if several employees have submitted a holiday request for the same period [image: 1716551536854-99._absences_for_approval.jpg] Individual requests can be accepted or rejected. [image: 1716551551049-100._absence_approval.jpg] In addition, absence requests can be processed directly in the calendar by simply clicking on the symbol with an asterisk in the calendar, the absence request opens and can be approved or rejected. The advantage of approval via the exclamation mark symbol is that several absence requests are listed, which may not be visible in the calendar immediately if they were submitted for different months. After an absence request has been approved, the asterisk * in the absence symbol disappears and the left margin turns black, i.e. the request has been approved but not yet finally saved. [image: 1716551575068-101._approved_absence.jpg] If an absence request is rejected, the absence icon disappears from the calendar immediately. The employee generally receives notifications in their own dashboard when a request is accepted or rejected. It is also possible to edit the absence calendar manually, for example if you want to add a sick note. To do this, select the relevant weekdays within the calendar, then select the appropriate one from the list of defined absence reasons in the upper area. The factors 1 and 0.5 stand for one and half a day respectively. Once the selection has been made, the symbol with the left black border appears in the calendar. This time it is not marked with an asterisk because this reason for absence has been entered manually. Again, this has not yet been finally saved. [image: 1716551585212-102._absence_by_hand.jpg] All changes (accepting and rejecting absence requests) are listed in a legend in the bottom right-hand corner and must be finally saved before leaving the module. [image: 1716551591012-103._approved_absences.jpg] As soon as you click on the “Save” button, you will be shown another change overview listing how many and which changes you have made. You can use the arrow next to the number to display details and thus check again whether everything is legal. [image: 1716551601028-104._change_overview.jpg] Once the absences have been finally saved, the black bars in the icon disappear.. [image: 1716551608372-105._change_overview_2_.jpg] 3. Time report [image: 1716551620619-106._time_report.jpg] After clicking on the “Time report” symbol, the following screen appears. [image: 1716551625415-107._time_report.jpg] Here you have the option of filtering by teams or departments. In the second option, a list of all employees is displayed, from which you can select one or more employees. Deactivated employees are not displayed for selection. In the third option, all employees can be displayed. You can also select a report type. The report can be selected monthly or for a specific period. You also have the option of using the arrows in the displayed calendar to scroll by year and/or select the months. Once all criteria have been selected, click on the “Request” button and the corresponding time report will be created. Below is an example of a requested time report for all employees for the month of January 2024: [image: 1716551634452-108._time_report_example.jpg] Using the drop-down menu in the name field (employees are displayed here in alphabetical order), you can select an employee and view their time report. It is also possible to scroll through the time reports month by month using the two red arrows on the right and left, regardless of which month was previously selected. In addition, you can use the two “Export” buttons at the top right to import the reports into an Excel file for further processing, for example to make them available to a tax office. The “Export All” button imports all time reports for the employees included in the selection into an Excel file. An Excel data sheet is displayed for each employee, the names of the employees are displayed in the tab labelled below. Only the time report of the employee currently displayed is imported into an Excel file via the “Export” button. The working and break times are shown separately in the time reports exported to Excel.
  • 5 Themen
    5 Beiträge
    thuthT
    COBI.ppc is a Production Process Control solution aka Manufacturing Execution System (MES) for SAP Business One, offered mainly in the form of an Android App. It is similar to and based on COBI.wms, but specialized for complex production workflows. Setup The following UDTs and UDFs are used by COBI.ppc. IMPORTANT: All tables should be of type ''No object with auto-increment''. Attributes In COBI.ppc we use the term "attributes" to refer to information about production orders that will be shown to the user. These attributes can come from a number of sources (see ''Origin'') and can be shown in the production overview screen, the production order details/execution screen, and in some step types. (See below for explanation of "steps.") Column Type Size Department Alphanumeric 20 RouteStage Alphanumeric 50 Title Alphanumeric 20 Origin Alphanumeric 20 FieldName Alphanumeric 254 PositionInOverview Numeric 2 PositionInDetails Numeric 2 PositionInSteps Numeric 2 The ''Origin'' can have the following values: Value Meaning RDR Sales order on which production order is based RDR_LINE Sales order line containing the item being produced WOR The production order itself ITM Item master data of item being produced CUSTOM Special The ''FieldName'' must contain the name of an SAP Business One object field with the name given to it in DI-API / Service Layer, not the name of the database column. For example, if the origin is ''RDR'', then it's fine to use ''DocNum'' because that's the name of the field both in the database and in DI-API / Service Layer. However, if the origin is ''WOR'', then you must use ''DocumentNumber'' instead, because even though in the database it's still ''DocNum'', in DI-API / Service Layer it's ''DocumentNumber'' instead. If the origin is ''CUSTOM'', the following values are supported for the ''FieldName'': Value Meaning __QUANTITY Completed & planned quantity displayed as X / Y __QUANTITY_WTR_PROD Transferred & planned quantities displayed as X / Y The ''<nowiki>__QUANTITY_WTR_PROD</nowiki>'' is useful if you don't want to consider a quantity to be truly completed yet before it's transferred to the target warehouse. See the "step" of action type ''ProdWTR'' below. Buttons When the user selects a production order from the overview, the details/execution screen will be opened for that order. In this screen, there can be up to five buttons with various actions attached to them. In the beginning all buttons are in the "Start" state. If a button has a ''TimeType'' value other than ''None'', then pressing it will switch the button into the "Stop" state and a timer will be started. The timer ends when the button is pressed again, or when a button of type ''Fault'' is pressed. PPC Buttons Type Size Id Alphanumeric 20 Department Alphanumeric 20 RouteStage Alphanumeric 50 Position Numeric 1 StartTitle Alphanumeric 20 StopTitle Alphanumeric 20 TimeType Alphanumeric 20 The ''TimeType'' can have the following values: Value Meaning Normal Regular production time Preparation Production preparation time Fault Duration of a fault situation None Button doesn't measure time If ''None'' is used, the button is always in the "Start" state. Steps We use the term "steps" to refer to one or more actions that can be tied to the clicking of a button in a certain state. This is how you can tie in actions like Goods Issue, Goods Receipt, and so on into the production workflow. For example, you might have a simple "Begin Production / End Production" button, which triggers a Goods Issue step when it's clicked in the "Start" state, and triggers a Goods Receipt when in the "Stop" state. PPC_STEPS Type Size -------------------- -------------- ------ Department Alphanumeric 20 RouteStage Alphanumeric 50 FirstStageOnly Alphanumeric 1 LastStageOnly Alphanumeric 1 ButtonId Alphanumeric 20 ButtonState Alphanumeric 20 Position Numeric 2 Title Alphanumeric 50 ShowAttrs Alphanumeric 1 ActionType Alphanumeric 20 ActionParam Alphanumeric 254 The ''Department'' and ''RouteStage'' fields, if filled, limit this step to the corresponding department (resource group) and/or route stage. The ''FirstStageOnly'' and ''LastStageOnly'' fields can be ''Y'' or ''N'' and only make sense if the ''RouteStage'' field was left empty. They limit the step automatically to the first or last route stage in a production order, without having to explicitly name that stage. The combination of ''ButtonId'' and ''ButtonState'' determines when the step will be triggered. The ''ButtonState'' must be ''Start'' or ''Stop''. (A button with ''TimeType = None'' is always in the ''Start'' state.) The ''Position'' determines the order in which the steps will be executed if they would both be executed after a button event. The ''ShowAttrs'' field can be ''Y'' or ''N'' and determines whether the display attributes of the production order should be shown in the step's screen. The ''ActionType'' determines what type of step this is, and can have the following values: Value Meaning AllItems List all item components of the production order MatsWTR Relocation of component items to be issued IGE Goods issue of the component items CompletedQty Enter completed quantity for current routing stage SimpleIGN Goods receipt of finished goods IGN Goods receipt with optional discarded/return items ProdWTR Relocation of received goods that were produced FillParams Parameter input screen (see below) Text Show the user a static text (e.g. instructions) Close Offer to close routing stage or production order The ''ActionParam'' can have different meanings depending on the ''ActionType''. The following table describes the meanings it can have. When there are multiple possibilities, they can be added together and separated with a comma. Action type Meaning of ActionParam IGE Comma-separated list of item groups to include ::: Start with ! to exclude instead MatsWTR Comma-separated list of exactly two warehouse codes ::: Determines the from and to warehouse CompletedQty IGNIfLast to call SimpleIGN during last stage ::: PreFillQty to pre-fill the quantity field ::: OverwriteQty to make the entered quantity overwrite the old ProdWTR Same as for MatsWTR FillParams Comma-separated list of parameter IDs Text The text that will be shown on the screen Close CloseDocIfLast to close production order during last stage (Note that the ''ActionParam'' has nothing to do with the "parameters" mechanism described below, except that for the ''FillParams'' action type it contains a list of parameter IDs.) Parameters We use the term "parameters" (not to be confused with "attributes") to refer to completely specialized values that users can input via a ''FillParams'' step, to document various information that doesn't fit into any standard SAP Business One logic. For example, you might have a "Tool State" parameter, and add a ''FillParam'' step to an "End Production" button where the user has to specify in what shape the tool is (fine, damaged, broken). PPC_PARAMS Column Type Size -------------------- -------------- ------ Id Alphanumeric 20 Name Alphanumeric 50 DataType Alphanumeric 20 ValidValues Alphanumeric 254 DefaultValue Alphanumeric 254 Mandatory Alphanumeric 1 MultiValue Alphanumeric 1 The ''DataType'' can be ''Text'' or ''Number''. The ''ValidValues'' is a list of comma-separated values. The ''Mandatory'' and ''MultiValue'' fields can be ''Y'' or ''N''. When a ''FillParams'' step is executed, the values given by the user are saved in the following UDT. Column Type Size Timestamp Alphanumeric 12 Resource Alphanumeric 50 EmployeeId Numeric 11 UserInfo Alphanumeric 20 WORDocEntry Numeric 11 RDRDocEntry Numeric 11 ParamId Alphanumeric 20 ParamValue Alphanumeric 254 Fault and rejection reasons The fault reasons will be shown in a drop-down when a user clicks on a button with a ''TimeType'' value of ''Fault''. The user has to select one of the reasons before the fault state can be ended. The fault reason will be saved in the ''Comment'' field of the ''PPC_WORSTATUS'' table (see below). PPC_FAULT_REASONS Column Type Size --------------- -------------- ------ Reason Alphanumeric 254 The reject reasons are shown in a drop-down when a user wants to add rejected quantities in a Goods Receipt, i.e. goods that were produced but are being discarded again for some reason, like being damaged. PPC_REJECT_REASONS Column Type Size --------------- -------------- ------ Reason Alphanumeric 254 Production status / timeline The following table records all button start/stop events so the price state in which a production order is, and for how long it's been running, can be seen. PPC_WORSTATUS Column Type Size -------------------- -------------- ------ Timestamp Alphanumeric 12 Resource Alphanumeric 50 EmployeeId Numeric 11 UserInfo Alphanumeric 20 WORDocEntry Numeric 11 WORDocLine Numeric 11 RDRDocEntry Numeric 11 PrevStatus Alphanumeric 20 Status Alphanumeric 20 ResourceGroup Alphanumeric 20 RouteStage Alphanumeric 50 ButtonId Alphanumeric 20 Comment Alphanumeric 254 In addition to the fields, it's recommended to add the following keys to this table for better performance: PPC_WORSTATUS keys Key Columns ------ -------------------- IX_0 WORDocEntry WORDocLine IX_1 ResourceGroup IX_2 UserInfo (To add keys to a user-defined table in SAP Business One, open the User-Defined Fields - Management window, find the table under User Tables, click on the ''PPC_WORSTATUS'' table, and then click on the Keys button at the bottom right.) User-defined fields Resources can be tied to a specific route stage (aka sub-department) via this UDF: Resource Master Data Column Type Size -------------------- -------------- ------ PPC_RouteStage Alphanumeric 20 Items can be declared to be of various types: ''Tool'', ''RawMaterial'', ''IntermediateProduct'', ''FinalProduct'', ''ByProduct''. However, currently only the ''Tool'' type is used. Items of type ''Tool'' will be automatically added to a Goods Receipt document as returned good. Item Master Data Column Type Size -------------------- -------------- ------ PPC_ItemType Alphanumeric 20 Since Relocation documents can't be based on a Production Order, the following UDF is used to specify for which Production Order they were executed: Documents Column Type Size -------------------- -------------- ------ PPC_WORDocId Numeric 11 PPC_User Alphanumeric 20 Times measured by COBI.ppc are booked as a Goods Issue with a Resource line; the following UDF describes what time of type this was (Normal, Preparation, Fault). Document Lines Column Type Size -------------------- -------------- ------ PPC_TimeType Alphanumeric 20 In the following UDFs, COBI.ppc stores information about the status of a routing stage within a production order. The UDF ''PPC_CompletedQty'' represents the quantity of items whose processing //within this routing stage// has been completed, although they may still have to go through other routing stages before they can be booked in as a Receipt from Production. The UDF ''PPC_Closed'' can be set to Y to indicate that no further processing will take place within the routing stage. Production Order - Route Stage Rows Column Type / Structure Size Valid values Default PPC_CompletedQty Units and Totals / Quantity PPC_DiscardedQty Units and Totals / Quantity PPC_User Alphanumeric 254 PPC_Closed Alphanumeric 1 Y / N N
  • 44 Themen
    75 Beiträge
    thuthT
    Print Service The COBI.wms Print Service is an MS Windows service which receives commands from the Android app and triggers a print event on the Windows machine. How it works / Limitations Currently, the service only works in combination with Coresuite Remote Print and Crystal Reports. The service generates XML files and puts them in a folder that is scanned by Coresuite Designer, which takes care of the actual printing. This means, you must have Coresuite Designer installed and configured correctly to pick up XML files from a specific folder. See here for the relevant Coresuite documentation: Coresuite documentation Only the User and Parameter Scan-Path fields need to be filled out. Also, if you don't have Coresuite Service, then at least one SAP Business One client must be running at all times for Coresuite Designer to process the XML files. See here for information about Coresuite Service: Coresuite Service (If either of the above links to the Coresuite documentation don't work, please notify support@cobisoft.de so we can update this page.) XML files that are placed into the folder will be moved automatically into a sub-folder called _executed if the print job was successful, or into a sub-folder called _error if there was a problem. (These folders are created and managed automatically by Coresuite.) In case of an error, you can open the XML file in the _error folder (with Notepad or another text editor) and see if an error message was written into it. Usually, Coresuite writes the error message into these files in the form of an XML comment, near the end of the file. NOTE: All of the above is done by Coresuite, not by the COBI.wms Print Service. If the XML files are not being processed, check if Coresuite is set up and running correctly. The job of the COBI.wms Print Service is done in the moment where the XML file is generated and put into the configured folder. Installing the COBI.wms Print Service First of all, make sure that a recent version of the Microsoft .NET Framework is installed. Download the program here: cobiwms-print-service.zip Extract the ZIP into a folder called exactly C:\cobiwms-print-service. Open the folder, right-click on cobiwms-print-service.exe and open its Properties. At the bottom of the Properties window, check “Unblock” and confirm. (If you can't see “Unblock”, skip this step.) Start cmd.exe or PowerShell as Administrator. Enter this command: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe C:\cobiwms-print-service\cobiwms-print-service.exe Create the file C:\cobiwms-print-service\config.json with contents like below. Note: Currently it is not supported to install the service under any other path than C:\cobiwms-print-service; please contact support@cobisoft.de if this poses a problem for you. After the service is installed and the configuration file is created, you can start/stop the service from the MS Windows Services application. Example config for single-tenant setup (e.g. on-premises or private cloud): { "ListenPort": 9110, "TenantConfig": [ { "PrintDirectory": "C:\\CoresuiteRemotePrint\\Productive" } ] } The PrintDirectory must correspond to the Parameter Scan-Path of the Coresuite Designer configuration; see above. Example config for multi-tenant setup (e.g. public cloud): { "ListenPort": 9110, "TenantConfig": [ { "AuthToken": "SECRET_1", "PrintDirectory": "C:\\CoresuiteRemotePrint\\Tenant_1\\Productive" }, { "AuthToken": "SECRET_2", "PrintDirectory": "C:\\CoresuiteRemotePrint\\Tenant_2\\Productive" } ] } In a multi-tenant environment, the correct AuthToken must be entered in the COBI.wms Print Settings screen for the app to be able to trigger print jobs. The token serves both to identify the tenant, and as a password to ensure that tenants running on the same cloud environment cannot accidentally or intentionally trigger print jobs for each other. NOTE: The COBI.wms Print Service does not support encrypted communication. This means that if you make the TCP port of the Print Service open to the Internet, and set up COBI.wms to contact it, then the tokens will be sent unencrypted over the Internet! It is strongly advised to set up a VPN connection in this scenario to ensure encrypted communication. Troubleshooting First of all, make sure that the COBI.wms Print Service and the Coresuite Service are both actually running. One or both of the services may have failed to start automatically after a server reboot. (If you don't have Coresuite Service, make sure that an SAP Business One Client with the Coresuite Designer add-on is running.) If XML files are appearing in the PrintDirectory defined in the configuration of the COBI.wms Print Service, but the printing isn't working correctly, check the following: Make sure the Print Definition ID and Layout ID are configured correctly in the Android app. See Print Settings. You can open the XML files with Notepad and verify the contents. Make sure Coresuite Service (or an SAP Business One Client with the Coresuite Designer add-on) is running and that it's configured correctly. If the XML files are not appearing in the PrintDirectory defined in the configuration of the COBI.wms Print Service, check the following: Double-check the configuration file. For example, note that you must use double-backslashes (\) in file paths due to JSON syntax. Make sure the COBI.wms Print Service is really running by using the MS Windows Services application. Make sure the TCP Port on which the Service is listening can be reached from the Android devices COBI.wms is running on. Use the MS Windows Event Viewer application on the server on which the COBI.wms Print Service is running, and navigate to Windows Logs –> Application, to see whether the Service is logging anything. (If there are lots of irrelevant log entries, you can filter the table to “Source = COBI.wms Print Service”.) If the COBI.wms Print Service is running but not logging anything at all, it means that it's not receiving any commands from the Android app, in which case double-check that the TCP Port is open and reachable from the Android devices. Otherwise, the log entries should tell you what the problem is. Updating Stop the service. Extract the contents of the new ZIP file into C:\cobiwms-print-service\, overwriting existing files. Start the service. Uninstall Stop the service. Run the following command in cmd.exe or PowerShell: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe /u C:\cobiwms-print-service\cobiwms-print-service.exe Delete the folder C:\cobiwms-print-service\.
  • Announcements regarding our community

    1 1
    1 Themen
    1 Beiträge
    thuthT
    Hello everyone, My name is Tim, and I'm excited to be a part of the COBISOFT Forum as a moderator and support specialist. Here’s a bit about my journey and role: What brought you to apply for a training position at our company? My interest in training with the company, particularly in the field of partner management, was sparked by an unexpected change in my career path. Through an educational organization, I discovered COMP.net and immediately applied. After mutual discussions, I was assigned to partner management. The warm welcome I received from the team solidified my interest in the tasks and responsibilities within partner management. Can you tell us about your daily tasks? Currently, I am still in the training phase within partner management. However, it's clear that I will act as a bridge between partner management and development. My primary responsibilities include first-level support for product inquiries and problem resolution, as well as assisting my colleagues in generating potential partner leads. Additionally, I work extensively with SAP Business One and our mobile solution, COBI.wms. I look forward to contributing to the forum and assisting the community with any questions or issues. Let's make this a great space for everyone! Best regards, Tim [image: 1718875942637-tim-huth-blog.png]
  • A place to talk about whatever you want

    4 4
    4 Themen
    4 Beiträge
    thuthT
    Here are some ideas and comments regarding the structure of the forum: 1. Create Forum Structure Main Categories: Create a unique category for each of your software solutions. This makes it easier for users to find relevant information and discussions. Example of a Category: Name: COBI.time - Mobile Time Tracking Description: Discussions and support for COBI.time, our system for revolutionizing the management of work hours and attendance. 2. Subforums and Topics Within each main category: Create specific subforums or sticky topics to organize discussions. Here are some suggestions: General Discussion: For general questions and discussions about the respective software. Support & FAQ: A dedicated area for support questions. Create a sticky topic with frequently asked questions (FAQ) to provide users with immediate answers to common questions. Feature Requests and Feedback: An area where users can provide feedback and request new features. This encourages community engagement and offers valuable insights for future developments. Updates and Announcements: An area for official communications about updates, patches, and new features. Keep this topic updated to inform users about the latest developments. 3. Guidelines and Moderation Forum Guidelines: Create a sticky topic with forum guidelines to promote a positive and respectful discussion culture. Moderation: As a moderator, actively participate in the forum, answer questions, guide discussions, and ensure that guidelines are followed. 4. Encourage User Engagement Welcome Post: An introductory topic welcoming new users and providing a brief overview of the forum can create a friendly atmosphere. Rewards and Recognition: Consider motivating active members with awards or other forms of recognition. 5. Feedback Cycle Regular Surveys: Conduct regular surveys to gather feedback on forum usage and user satisfaction. Use this feedback to continuously improve the forum. By following this guide, you create a structured and engaged community that not only provides support but also valuable feedback and ideas for the further development of your products.
  • Got a question? Ask away!

    0 0
    0 Themen
    0 Beiträge
    Keine neuen Beiträge.
  • Blog posts from individual members

    1 1
    1 Themen
    1 Beiträge
    thuthT
    COBISOFT has been awarded as ISV of the Year! Honoured for our work in the EMEA North region, the citation singled out COBISOFT 's contribution to SAPBusinessOne. It is a testament to the hard work and efforts across the whole team - our developers, consultants, partner and account managers, as well as marketing. We extend our sincere gratitude to our amazing partners such as ANG , Cloudiax , conesprit GmbH , neumeier AG , OSC Smart Integration GmbH , Profiz , SideStep Business Solutions GmbH , SIGMA Software und Consulting GmbH , WUD - IT & Business Software , XEGO-it GmbH , Versino AG , V-Chain SA - Member of the Ando Group , White Sheep GmbH , Anrova Solutions , DDI Group Consultancy Ltd. , Be1 SAP Business One , OSELA Technologies Limited , Argentis Consulting | SAP Partner , KOOMBA b.v. , Sonoma Consulting México , SUPREMIS Sp. z o.o. , ONE ID , Force Net GmbH , Konsultec , Liberali - SAP Gold Partner , wp.DATA Kommunikations GmbH , CP Wave GmbH and many more! Your unwavering support and great collaboration have been indispensable in helping us achieve this accomplishment. Once again, thank you for your invaluable partnership. We also really appreciate our close working relationship with SAP - particularly Marc Siefert, Isabel Ostermeier, Jan Lukas Papst, Larissa Schaan, Mario Fetzner, Darius Heydarian and Karsten Rachholz and many others whose help and support has really helped drive the success of our participation as an ISV for SAP Business One! [image: 1709891246142-isv.jpg] [image: 1710151340818-testt.jpg]