# TQ routing API changes

1. Project creation and editing (added new param)
new_param = tq_route(bool)
url :- http://localhost:5000/v1/project(post, put)

2. New user invite (added new roles)
new roles can be sent as params (procurement, project_coordinator, lead_engineer, project_manager)
already present roles (project_engineer, admin, default_user)
http://localhost:5000/v1/user/role/update
body ({"new_role":"default_user","emails":["[e-mail]"]})
new roles while invite user in "role" param (/v1/invite)

## When saving Query from PRC save it in collab and also add it to tq_ids in vendorview for prc. need to use email and offer_id to get the vendorview.

### Can forward to RE email (that is being sent to RE) fail if the offer was uploaded by vendor with prc flow?

{"vendor_name":"6","mr":"61f7b7c1aacbc3648de5c7bc","file_section":[{"section":"603dda9ed2a3ee911b70e283","file":"Sulzer Offer - 3 Tags - Deleted tags from common scope_164371608673466.pdf"}]}

# remember to change DB save for vendor view when prc publishes MR to vendor

# RHS

Cycling synonyms :- Changing core logic and database structure ~ 15-16 hours with solution, implementation and testing

Changing current apis or creating new apis - Changing current apis to show '4' column containing list of synonyms in MSA and MSC offer listing ~6-7 hours with testing.
New api time depends on Frontend.

For the below things we will need to change the database structure for optimal execution like we will need to extract the text from pdf and that text will be required in subsequent apis so we can store the text and also the dictionary that we are storing the page number. Setting DB structure

Summary page :- Create new api for summary page identification. MSA and MSB :- 4 hours for MSA(GET and PUT) and 14-15 hours for making change in DB and logic writing for MSB.

Tag identification :- Create new api for tag page identification. MSA and MSB :- 4 hours for MSA(GET and PUT) and 18-20 hours for code solution, implementation and testing.

Integrating all this with our current extract offer api and testing 2 hours.

Starts from the same line when we find group synonym

For finding next group we start from next line

and go till we find an other synonym
but group coloumn end is always the end of the datasheet.

Started with a monologue and then when asked some question just throwing out big words and references.

if "3" not in this_ind_offer_df:
this_ind_offer_df["3"] = ""
+ if "4" not in this_ind_offer_df:
+ this_ind_offer_df["4"] = []
try:
mr_join_obj = JoinManage.objects.values().get(
{'mr':ObjectId(mr_id)}
@@ -2366,7 +2368,10 @@ def get_merged_mr_offer(this_ind_mr, this_ind_offer, mr_id):
for index, row in this_ind_offer_df.iterrows():
this_ind_offer_df.at[index,'0_processed'] = str(row['0']).replace(" ", "").lower()
this_ind_offer_df.at[index,'1_processed'] = str(row['1']).replace(" ", "").lower()
- this_ind_offer_df.at[index, 'cyclic_count'] = len(row.get('4', []))
+ try:
+ this_ind_offer_df.at[index, 'cyclic_count'] = len(row.get('4', []))
+ except TypeError:
+ this_ind_offer_df.at[index, 'cyclic_count'] = 0

IF PRC is added to project then he can see all the requestions right, if not then how can he get.
This was tested by QA team too.