K2A,

 I am unaware of any rules that will automatically deploy a package using rules within a form. However, there are workflow rules which will allow you to create, update, and delete lists. You may also change the permissions of a list using the workflow. 

Under the file tab in Workflow Designer there is a tab that says General. If you this tab a dropdown appears which gives you an option for Lists. When "Lists" is selected the ribbon changes to show the list options.  

I am curious what exactly you would like to deploy using an automatic deploy rule. Maybe there is an alternate way to accomplish what you are trying to do.

Thanks,

Bryan Peters

Thank you so much BryanPeter..

Actually, I'm  trying to duplicate the list with same SamrtForms and Views once SharePoint list reached threshold list item.

Consider, SharePoint List threshold is 5000 items.Once 5000 items have been reached I have to create a new list with the same template.

K2A,

 I know exactly what you are running into. Because of this roadblock we started creating tables directly in SQL and creating Smartobject directly from the SQL table. In fact after we did that we asked ourselves why were even had K2 integrated with SharePoint. So we removed the K2 integration and started using a SQL backend. We no longer have to worry about the thresholds within a SharePoint list. I understand your environment might be restricted in that regard. If you cannot create a SQL table and a smartobject outside of your SharePoint environment then your only other option might be to increase the threshold of the SharePoint list. I know that is not the happy answer but I am unaware of a way to duplicate a Smartobject automatically and start writing to it. Especially doing all of this automatically with rules in the form. If you would like some guidelines on how to create the SQL table and create a smartobject out of the table then consume it in the form please let me know. I will be happy to provide that for you. I really think that is the best way to go. There will be no limits to the number of items in the database so no worries about a threshold.

Thanks,

Bryan Peters

Thank u so much Peter....

but in our organization, they are restricted the threshold limit to avoid performance issues that's why we trying this approach. 

And one more thing this approach already was done using Nintex Workflow. 

Now we are moving Nintex to K2 for SharePoint.

Anyway thank you for your time...I will let you know if i have any further more doubts... :)

I have been working on k2 from last 6 years and I love K2.  Yes, It is really painful integrating SharePoint and K2. Below are my own opinion and I am not affiliated or promoting any product.

1. Initial development is fast but it bites you back soon once the application starts growing and your options become narrower and limit ways to solution the problem.

2. Each and every time you will have a problem while upgrading SharePoint or K2 and in the case of Nitext, I can imagine it would be a lot painful compared to K2.

3. You are going to face same issues same as Nintex using K2 for SharePoint down the line. Lack of governance, security for k2 for SharePoint would mess up the both K2 and SharePoint environments.

4. I believe k2 for SharePoint is there only for selling strategy and to compete in the market as people want low code applications.

5. k2 for SharePoint is only useful for small applications where you do not expect application will evolve in future.

6. If project size is large and keeps evolving, I will go with SQL database and also at some places would avoid using smartforms too. Instead, use asp.net for UI, it gives you flexibility and does not restrict your imagination.

7.  No doubt K2 workflow engine is robust and would always love k2 for smartobject and their workflow technology.

I can go on but above are main points to stay away from K2 and SharePoint. As a developer, you can keep developing these solutions and eventually migrate to SQL and keep doing you job, no harm to you!! :)