K2 Five

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Tools or Features in the package & deployment

    Tools / Features in the package & deployment console to select items or artifacts or objects that are added / modified / updated to a certain vulnerable time

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  2. K2 Package and Deployment involves Custom Workspace deploying

    Custom Workspace is always used by K2 Five Workspace user. But when the menu added on the test/dev environment, I have no ideas to transfer it to the proc environment. Can the Custom Workspace settings can also be involved in the package that we can simply deploy the Custom Workspace and encourage us to use it.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  3. Category Security with P&D causes difficulty for non-Admin users

    Today, creating packages requires full access to all categories. This creates security concerns as one do not want the whole environment open. P&D should allow users to browse what they are allowed to see in Designer (as set up using Category Security). This means there should not be any referenced items that users do not have access to (Designer will restrict this) but if restricted items are found, warn the user and either prevent the items from being included or add the items by Ref.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  4. Refresh SharePoint description on Target Environment

    There are some challenges with SharePoint deployment, any differences on SP artifacts on the target environment will raise issues since the artifact definitions will not match. Let P&D refresh the artifact resources before deployment to simplify the process. If not, it becomes a more complex process which can confuse CitDevs where they will need to go to the target List or Library, go to the K2 app and then update the SmartObjects from there.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  5. Split the P&D role into two roles

    Split the P&D role into two, rights to Create packages and another to Deploy packages. This allows for more granular control as the ones building apps (Cit Devs/Devs) will also need to create the packages to be promoted to the other QA/PROD etc. but should not have permissions to deploy packages (Ops/App Managers).

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability for P&D to handle merging better during package deployment

    If or when two solutions share a common artifact i.e. View, with rule(s) configured at the Form level. When deploying the two solutions to the same target environment, whichever of the two packages get deployed last will maintain the Form level rule configuration.

    This is a known issue with P&D in the area of extended rule merging (where the rule is added onto an existing view event from the form context) when the relevant SmartForms artifacts is shared between artifacts for instance, as described in more detail on http://jhbtfs:8080/tfs/labs/WorkItemTracking/WorkItem.aspx?artifactMoniker=862760

    User Story: http://jhbtfs:8080/tfs/Labs/K2%202014/_workitems/edit/907694

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  7. Deployment Activation Feature

    It would be great if K2 allows the deployment but not to activate right away. Similar idea as Salesforce where you can move changes to one environment to another but also allows you to when to activate that change. Also K2 should allow inter connect on environment as automated deployment instead of using Package and Deployment. You can schedule you change ahead of time and validate in advance. Then K2 can save the configuration and feature/setting you have selected on scheduled deployment time and auto deploy the change.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  8. Compatibility for Document library with over 5,000 items in SharePoint 365

    We are a large enterprise and our document libraries get fairly large. We properly index columns but package and deploy can not create a smart object on a document library that has over 5000 items in it. Currently the package and deploy presents the error: "The number of items in this list exceeds the list view threshold, which is 5000 items."

    Is it possible to use the Microsoft.SharePoint.Client.dll to iterate over the columns and create these smart objects instead of using a CAML query? This would allow K2 to be used on any SharePoint 365 document library instead of just…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  9. Package Version Selection on Package and Deployment Tool while packaging

    Currently if we upgrade k2 version for instance from 5.2 to 5.3, all forms, views and smart objects get force upgrade to 5.3 and there is no way we can create a package which is compatible with 5.2 afterwards. This will cause a problem for us as K2 GSI or delivery partners when we have a common solution which we like to deploy it to different customers but the customers are using different K2 versions as we have to maintain the common solution in several K2 versions to make packaging into different versions possible hence it would be very helpful…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  10. Additional filter criteria and display columns on Package and Deploy Utility

    I would like to see the ability to filter items (by name, category, type) within the P&D interface to more quickly drill down on the items I need to package.

    Also, including the Last Modified Date and allowing sorting on that column would speed up the process of identifying items that need to be included in a package.

    Finally, even when the option to include related items as references is selected, and only non-Process items (View, Forms, SMOs) are selected, processes are still included as items rather than as references and need to be manually changed to Pacakge by Reference.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  11. Exclude disabled rules and action on creating package during reference check

    When disabling rules or actions and try to create a package, the tool will output all the referenced objects to the package, even though the rules or actions are disabled.

    It would be very nice, if the reference check after selecting Objects would ignore the disabled items.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow P&D to package service instances

    This used to be in an early version of P&D. It would be helpful to deploy batches of service instances between environments. If not P&D, then some other kind of export/import capability, maybe in the services tester tool.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  13. Only allow developers to create deployment packages for the apps they have security to

    We have developers that do not have administrative access to K2. I would like to secure what applications they can modify and package for deployment. Currently if I secure them from anything in designer they are unable to create a deployment package for their respected applications. Developers only create deployment packages and do not deploy them, only administrators do. Why can the security follow through to the Package and Deployment Tool?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  14. Easy method to select modified objects to include in a package

    Wouldn't it be really great if there was a right click option when selecting a category to include in a package, whereby you could specify a date so that items modified since that date are selected for you. Tedious at the moment have to reference the output of a SQL query identifying all those objects from a spreadsheet.

    Even better to then capture that information as part of the package file and provide another option in the MMC, besides Edit, whereby I can select the package and choose Refresh, which will use the same date to update the package, without…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  15. Deploy with delayed activation

    In order to deploy without interruption of service, I would like deploy packages during working day but activate the new objects versions deployed at a define date and time (when nobody is connected) or by a script powershell.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  16. Export process definition to plain text file

    It would nice if the K2 5.1 Designer offered a mechanism to export the process definition as a plain text file which can be checked into a version control system so we can review changes between versions.

    See https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  17. Package & Deploy roles which are not assigned to workflows

    Hi there,

    when you deploy a package, only the roles which are used in the workflow will be deployed. But not the roles you create and use for example in rule for the view. So you have to create every single role on every enviroment. could you please fix this?

    Thanks Alex Stroica

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  18. Include Custom Broker in the package

    The P&D tool allow us to include Service instances.

    It would be useful to include DLLs associated to custom broker when a service instance of a service type is included.

    This would ensure that we always have the latest version of the broker when deploying to other environments as we often work with custom brokers.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  19. Include Custom Workspace with Package in P+D

    It would be very convenient if you could package a Custom Workspace with your K2 Application. This would likely tie into creation of a unified "App Container".

    Currently, you have to re-create your custom workspace in each environment after performing a package and deploy of the K2 application, which is somewhat inconvenient.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
  20. Improve error message at the end of the deployment by "Package and Deployment" (P&D) when a SmartObject is invalid

    When we import of P&D and one of the smart object imported is not valid, we have the following error message: "Package deployed with dependency error".
    In event viewer:
    I found the following error message in event viewer: "30101 Logging Framework Error, MsgID=30101 (Message Not Found)"
    or
    30101 Unable to create dependecies for SmOReportsReportRequest SmartObject. Additional Info: ServiceObject: ReportRequest; ServiceType: SourceCode.SmartObjects.Services.Endpoints.Rest.Broker
    Repo steps:
    1) Create an SQL table "TheTableToDelete"
    2) Create a Smart Object based on this table
    3) Create a view based on this smart object
    4) Package this view/Smart object
    5) Delete (or rename) the SQL…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Package & Deploy  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base