Messages

46

General Board / Re: Traceability Window contents in Reports

« on: March 26, 2013, 12:36:07 am »

Hi

What I found work around was to add the Element section. Then i added a table inside that section. Then added the Element fields - Name, Type & Realizes in the 3 columns of the table.

The only thing - as per in Traceabililty Window how we have "implements" that I am not sure how to put in it the report.

Else for now, I could do it this way.

If anyone has more on this, please do share.

47

General Board / Re: Traceability Window contents in Reports

« on: March 23, 2013, 04:18:07 am »

Hi Robert

I did include the connector section in the report. But I am not exactly sure how to use them...When i saw the output file..there were few things repeated and it didn't made sense.

can you provide me an example?

Thanks
KN

48

General Board / Traceability Window contents in Reports

« on: March 19, 2013, 02:20:57 am »

Hi

As we know that there is way to view the traceability of elements in EA..i.e. the Traceability Window.

Is there a way that i can get those contents in a report?

Does the Dependency & Implementation report serve the purpose? If so, how to view these reports at element level (they can be viewed at Package level).

Thanks
KN

49

General Board / Business Process Diagrams report

« on: March 23, 2013, 07:15:24 am »

Hi

I have 3 high level business process diagrams. And within that say each has 5 sub-processes.

I want a report where I only want the name of the diagram and just the sub-processes it contains.
I tried creating RTF template from scratch. I included the Package section, then Diagram section and within Diagram, Element subsection. But this lists all the elements in that diagram (including pools, lanes etc). Also, I tried doing filter - but there is no option for Diagram Element filter.

How do I get the report - just the names of high level business processes and its sub-processes.

Thanks
Kesha

50

General Board / Re: Limit "Export" functionality

« on: March 20, 2013, 08:02:47 am »

I know you would have found this a stupid question. But because I didn't wanted to have user security enabled as there are many users (will have to create that many user ids and passwords)...so thought whether there was any solution at database level.

51

General Board / Limit "Export" functionality

« on: March 20, 2013, 06:58:59 am »

Hi

I have a DBMS repository setup.

Is there a way that I can limit the Export functionality without enabling the user security?
in other words, I dont want to enable security but want to limit few functions. Can this be done through the DB itself?

Thanks
KN

52

General Board / Re: User Security in EA

« on: February 28, 2013, 01:53:45 am »

@qwerty: I was doing the way you suggested but probably i just put the same things in my words....and also its my first extensive experience with EA ...thnx for yr guidance  

53

General Board / Re: User Security in EA

« on: February 27, 2013, 08:42:29 am »

Thanks qwerty!!

Thts what i was testing right now....its working actually....the only i m figuring out is how to have a master admin...who has control on all projects root nodes/assign users to group/create group etc....found a way to that too....the admin needs to have separate login for each group...

what do you think can be other way?

KN

54

General Board / Re: User Security in EA

« on: February 27, 2013, 04:15:05 am »

so with the scenario that i mentioned in my first question about users updating/deleting elements from other project can be maintained with locks...right?

55

General Board / Re: User Security in EA

« on: February 27, 2013, 03:49:22 am »

What is the difference between Manage Locks and User Security?

56

General Board / Re: User Security in EA

« on: February 26, 2013, 06:51:03 am »

Thanks everyone for the reply
Still have to try the options

Will update once I do so.

57

General Board / Re: User Security in EA

« on: February 23, 2013, 07:09:19 am »

I did that...i created Group A - giving that group certain permissions and then i assigned that group to user a.

My concern is because there are many projects within one repository and there are diff teams for diff projects. Hence, say project team of Project A should not be able to see Project B data.

So what permission in Group A (giving such a name to correspond to the project name) should i give that the above is possible - that users in Group A should only be able to Project A data but not other projects - atleast update/delete...

58

General Board / User Security in EA

« on: February 23, 2013, 06:46:24 am »

Hi

I have One repository with multiple projects (root nodes) say for eg - A, B & C.

I have enabled user security and created groups similar to project names. I have assigned few users to these groups.

For example:

user a - Group A
user b - Group B
user c -  Group C

How can i control these users accessing other project data? Like user a should not be able to view/update/delete any of the Project B or C 's data.

Is there a way that the group we created under the project security can be linked to the project root nodes names in the repository?

Thanks
KN

59

General Board / Subversion and EA repository

« on: February 22, 2013, 06:18:22 am »

Hi

I have a MySQL repository integrated with EA and using SlikSVN for the version control.

I had a project A (for example) in the repository and had assigned package control (a1.xml) to one of the packages in the project.

Then, for some reason, i made a project transfer (for example Project B) to the DBMS and the old data (project A) gets wiped off from the DBMS. I never changed/deleted the associated version control file.

Is it possible that i can sync Project B with the latest version of project A i.e. a1.xml?
because when i try applying package control in project B pointing to the same a1.xml file it gives me a warning that "file already exists".

Let me know if you have any questions or anything is not clear

Thanks
KN

60

Bugs and Issues / Re: MySQL ODBC driver

« on: June 04, 2013, 11:27:58 pm »

Thanx Dermot!!!

will try with that version.