I have a very big problem after migrating BPM from version 8.5.5 to BAW 22. I have a saved search on the process portal, which shows me the tasks of all users broken down by process. After migration, this search has stopped working and it only shows me my tasks and the team tasks I belong to. It stopped showing other users tasks. I tried to fix this error in different ways but nothing works. Can anyone help?
Can you provide more specifics on what you have tried so far?
Two things I would suggest:
If search optimization is enabled, check out this link here if you haven't already. You will need to drop the LSW_BPD_INSTANCE_VAR_NAMES and LSW_BPD_INSTANCE_VARS_PIVOT tables and recreate them using the steps mentioned here:
https://www.ibm.com/docs/en/baw/22.x?topic=portal-tuning-process-searches
2)Depending on your Saved Search criteria, it's possible you will need to re-create it. See the red alert section about existing saved searches and migration here:
https://www.ibm.com/docs/en/baw/22.x?topic=windows-restarting-verifying-migration.
It mentions 'earlier versions of Business Automation Workflow' but the same would apply to earlier versions of BPM
Related
I have been working with a Startup project from Scratch for around 2 year and this is my first project. The project is quite complex with many business logiŃs and have thousands of lines of code.
One of the function of the project is that people can place their items on the map to show them to other people who can collect these items. The owners of these items can edit them by editing the name, description and also change the item location in map. Everything works fine when I test in the development server and in the production server.
But, sometimes, when our client is editing the location of the items in the map, server couldn't save the location at Database and the location list of this item becomes empty (I, myself, can't reproduce this error). I am trying hard to figure out the cause for this issue, unfortunately I could not find the bug.
I have tried these function to save the location of the item,
locationRepository.save()
locationRepository.saveAndFlush()
but all are in vain. From time to time, the error is being shown up and the item's location list becomes empty. Probably it worth noting that there are many lines of code in the location edition function to check item number and their costs and some other necessary checking.
There is not any high load in the server so that server could break down.
Could it be that there is some relation between the Spring Boot version or PostgreSQL version? Or it's a bug in my code which I failed to find.
PostgreSQL version: 10.15 (Ubuntu 10.15-0ubuntu0.18.04.1)
Spring Framework version : 2.1.1.
Java version: openjdk 11.0.10
If you would have any thoughts, ideas, or insights regarding to this issue, please share them.
I would really appreciate your help.
I was having some trouble bulk-loading records to go faster than what cursor.executemany would allow. I hoped the bulk operations documented with regular MonetDB here might work, so I tried an export as a test. e.g. cursor.execute("COPY SELECT * FROM foo INTO '/file/path.csv'"). This doesn't raise an error unless the file already exists, but the resulting file is always 0 bytes. I tried the same with file STDOUT and it prints nothing.
Are these COPY commands meant to work on the embedded version?
Note: This is my first use of anything related to MonetDB. As a fan of SQLite and a not-super-impressed user of Amazon Redshift, this seemed like a neat project. Not sure if MonetDB/e is the same as MonetDBLite - the former seems more active lately?
Exporting data through a COPY INTO command should be possible in MonetDB/e, yes.
However, this feature is not working currently. I was able to reproduce your problem, i.e. the COPY INTO creates the file where the data should be exported to, but doesn't write the data. This does not happen with regular MonetDB.
Our team is notified of this issue, and we're looking into it. Thanks for the heads up!
PS: Regarding your doubt about MonetDB/e vs MonetDBLite: our team no long develops and maintains MonetDBLite. Both are embedded databases that use MonetDB as the core engine, but MonetDBLite is deprecated. After having learnt some do's and don'ts with MonetDBLite, our team is developing our next generation of embedded databases.
So for your embedded database needs, you should follow what's coming out of our MonetDB/e projects.
I've created a test for it at: https://github.com/MonetDBSolutions/monetdbe-examples/blob/CI/C/copy_into.c
Also filed a bug report over on GitHub: https://github.com/MonetDB/MonetDB/issues/7058
We're currently looking into this issue.
An action was taken last month to delete deployments from an Application that was made available as required install earlier last month. There are no longer any deployments associated with the package but some users have reported that they just got the application installed on their computer from the same package.
Not sure why would that be as there are no associated deployments with the package anymore. The original application package was pushed out to user collection.
Any help identifying potential causes would be greatly appreciated.
You can try installing the Configuration Manager Support Center on a model device, then search the Content tab for the application.
If it does appear there, it might indicate a problem with policy update. Check the PolicyAgent.log and PolicyAgentProvider.log for possible errors.
It may also be because of dependency / supersedence, check the references tab in the application's Properties.
If it does not appear you can check the AppEnforce.log to verify that the application installation was performed by the SCCM Agent, and at what time.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I hope that somebody with more experience (bad or good) can help me out here: I am setting up a project tracked in JIRA. The whole process with user stories, documentation, sprints, workflows, bamboo and fisheye integration, etc. is set up. But now I have a rather administrative question:
Where should developers log their work in meetings, such as stand-ups and retrospectives and for writing specifications (detailed descriptions of user stories to come)? I really cannot see what makes sense here, as I need the developers (obviously) to track this work, too. As far as I can see, the possibilities are:
Separate PROJECT-ADMIN JIRA project with simple, non-agile issues
Separate and parallel sprint with admin tasks
Administrative tasks for each sprint
Other versions??
Option 2 seems very hackish, as parallel sprints are just in a beta-stage for the JIRA agile (former Greenhopper) module. Option 3 seems a bit much work to setup for each sprint, and I am not sure, how this influences my velocity (ideally, I want to see the possible amount of story points that can be achieved in a sprint). Option 1 seems the most reasonable to me, but others have advised against it, unfortunately, without offering a solution. I haven't really looked into option 4, as IMHO this is very similar to option 2.
I couldn't see any best practices anywhere, so I would very much welcome any advice from more experienced people. Thank you very much.
We use Tempo to log our billable work against JIRA issues, whether a single Epic for a small project or individual tasks for a larger project. For non-billable work we have a single project where people can optional log work, and we also use it for planning our time. So option 1 is the closest there. We could also have categories for different work logged in Tempo and handle this case that way.
So I face this exact issue with my team and this is what is working for us (for now) YMMV.
Our current structure is that we have a Roadmap type project (call this Planning) where all issues come into at first. Thereafter we create issues in related product projects (call this Product).
In the beginning of the lifecycle, any meetings, scoping, etc will have sub-tasks created and the time will be tracked on Planning. Once scoped and scheduled for work a new issue is created on Product and linked to this original issue.
Once the Product issue is assigned and the dev is called to any meetings whilst this issue is in a sprint we will create a sub-task on Product and assign the time. If the issue is not in a sprint we go ahead and create a new sub-task in Planning and assign the time there.
When then also have a project where we do Housekeeping type work. So if we need changes to JIRA, Stash, Confluence we will create the issues here. We will then create a new issue on Planning, link the issue and schedule that accordingly.
We have a meta project that acts as a bucket for anything that doesn't fall into the other categories which we sift through every now and again to identify if we need to create separate projects.
I have created a custom field that rolls up all the times of any linked issues found on the Planning board
Have a look at the Twitter blog Visualizing Epics and Dependencies in JIRA by Nicholas Muldoon maybe this can help you in some way too.
One caveat we are still exploring the best way to do this. Each environment is different and what works for us might not work for you.
I have faced the same issue trying to track team member hours that are unrelated to the project or related to the project but not to a specific story or task.
Initially we went with option 3 & had several administration tasks that persisted across sprints. While this was relatively easy to implement it failed for us as we had team members that sat across multiple projects & as a result these administrative tasks that resided in each project were impossible to manage / report on for these team members.
In the end we went with what you have described as option 1. By creating a separate project with "non task related" issues such as Planning Meetings, Technical Issues & Client work then installing the JIRA Misc Time Log & Report Extensions plugin we could provide users with an easy means of logging times without having to change projects or boards (since the plugin adds a dropdown menu to the top navigation).
The plugin then allowed us to get reports on where team members we logging time off project regardless of how many projects they worked on concurrently.
I was having the same issue, and I know some time has passed since the moment this question was posted but maybe this is useful for a lot of people:
Tempo has a dedicated feature for that thing you want to achieve and is called Internal Issues. not to be confused with Internal activities.
You can go there by navigating to Config>System and then click on the add-ons tab. Then scroll down to the Tempo section in the menu on the left bar and there you'll find a link that reads Internal Issues. There you can create the issues. Please keep in mind that before creating internal issues you have to create the tasks, for instance "Sprint Planning" or "Retrospective" in the project without assigning to anyone, just to the project.
When your users go to log their time for those "Internal Issues" they go to Tempo > Timesheets and then click in the upper right button that reads log work. There, in the right menu they'll see the "internal issue" option where they can pick those internal issues you previously created and log the time that the team spend on SCRUM Ceremonies.
We have an internal installation of Agilefant. We are done with the first sprint and already started the second one now our client asked access to Agilefant so he can check our progress. The problem is that we have multiple projects inside of our installation and we don't want them to see the other projects:) You can understand that:)
If I'm right you cannot restrict an Agilefant user to have access only for one product, he will see all of them (please correct if I'm wrong).
So the solution is to make another installation and somehow migrate the project to that installation. Is there an easy way to do this?
I'm open for other solutions.
I've got a great answer for my question from jarno a site administrator on the Agilefant Community Forum. There are no easy ways to achieve a product's migration yet. Although jarno described two ways how you can do it:
a) You can take a copy of your database, put it into another Agilefant instance and delete all products that you don't need. Then you can create users for your client.
b) You can adopt Agilefant 3.0 alpha X. You will be able to restrict product access based on teams with Agilefant 3.0 alpha X!
You can find more details and known issues with this version of Agilefant on the link below:
http://agilefant.freeforums.org/how-can-i-migrate-a-product-from-an-agilefant-installation-t205.html